Changes required to make yoyo work with MS SQL Server 2014

Had to use MS SQL Server 2014. Existing implementation nearly worked but had to make some changes. I have it working here: https://bitbucket.org/johncant/yoyo/branch/hack but want your advice on what you'd like in a pull request.

Here's how I got MS SQL working without having to use $#%&dows:

vagrant plugin install vagrant-vbguest
vagrant init msabramo/mssqlserver2014express
vagrant up --provider virtualbox

One issue is a straightforward bug or my misuse on my part The other issue is that you're not allowed to set TIMESTAMP columns in SQL Server.

bitbucket:John Cant
Assigned to
8 years ago
4 years ago
No labels applied.

bitbucket:ollyc 8 years ago · edit

We need to think about how to change the db creation SQL depending on the target db. I think refactoring and extending the connections.py code is the way to go here.

Rather than having simple functions each returning a db-api connection, we will probably need a class for each db type, containing both the connection code and any db-specific SQL commands necessary to create the migrations table.

I don't have time right now to think about how I'd do this, so if you want to create a pull-request for this that'd be great. Otherwise I'll have a look when time allows.

bitbucket:John Cant 8 years ago · edit

See pull request #5

Register here or Log in to comment, or comment via email.