Plans to support MSSQL?

[ravensorb]

Curious if there are plans to support MSSQL, especially now that it runs on linux. This would be a huge value add.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[wzrdtales]

@ravensorb No, none. But, I designed db-migrate in the late versions to provide the most possible freedom to the community. Drivers are external, so everyone can just freely write their own driver. So if you're in a big need for it. It is not too hard to write a driver for old standard SQL databases like MSSQL is.

I dedicated a section in the docs for this:
https://db-migrate.readthedocs.io/en/latest/Developers/contributing/#creating-your-own-driver

You can also look in the organisation at the other drivers for examples: https://github.com/db-migrate or even search in npm for community drivers. A driver always needs to start with the prefix db-migrate- so they're easy to find.

I will flag this as a feature request and with help wanted, since I wont invest work here. You could however also put a bounty on this issue via https://www.bountysource.com/, if the invested time gets payed I will also dedicate some time for this request or someone from the community, but I don't have enough time to spend them on all community request, also I would love to do so.

Feel free to reach out should you have any additional questions.

[christiaanwesterbeek]

@ravensorb @wzrdtales I've built one today. Here it is: https://github.com/devotis/db-migrate-mssql

I started from a fork of https://github.com/db-migrate/pg . Took me about half a day to build it, and it's working. Without transactions for now. I'm sure there's room for improvement though. If you want to try, run: yarn add @devotis/db-migrate-mssql

I've not adapted the tests from pg to mssql yet, so no guarantees, but I'm able to migrate up and down. I tried only runSql thus far.

[christiaanwesterbeek]

@wzrdtales Running into a problem here. Somebody already published db-migrate-mssql, but they did half the job since it's not working. I redid it from a fork of pg and it's working, but since the name db-migrate-mssql is already published at npm, I had to scope-publish mine at @devotis/db-migrate-mssql. But now when I use the driver mssql to migrate, db-migrate is telling me:

Error: No such driver found, please try to install it via npm install db-migrate-mssql or npm install -g db-migrate-mssql

And that's correct, but the driver IS installed, just not under the conventionalized name. How about adding a repository configuration for that? Something like:

{
  "prod": {
    "driver": "mssql",
    "repository": "@devotis/db-migrate-mssql",
    "user": {"ENV": "PRODUCTION_USERNAME"},
    "password": {"ENV": "PRODUCTION_PASSWORD"}
  },
}

[christiaanwesterbeek]

For the time being, you guys can add this to your package.json and than yarn/npm install:

"db-migrate-mssql": "https://github.com/devotis/db-migrate-mssql",

So, don't do yarn add @devotis/db-migrate-mssql for now, and if you already did, remove the line "@devotis/db-migrate-mssql": "1.0.1", from your pacakage.json

[wzrdtales]

Hey, sry for the delay. Today is again some Open Source Time free for me.

I will add support for name scoped packages. Have nothing to argue against that in general.

[wzrdtales]

@christiaanwesterbeek Btw. always try to reach out the npm support and report them an inactive package. Of course try to contact the mssql package owner first and ask him to transfer it to you. Most people will gladly do that if their package is not being maintained anyways.

[ryd0rz]

Hi, I work for a company named Level Up Development, and we published the db-migrate-mssql to allow db-migrate MSSQL support for several internal projects we are currently developing.

@christiaanwesterbeek - If you'd like to be added to our git repository as a collaborator - we'd be happy to add you, to help further the support for db-migrate's compatibility with MSSQL.

Reason we chose to extend support to MSSQL is because we believe DB-migrate is the first npm package to have written a database migration tool the right way.

Currently we've only added support for SQL script migrations - looking forward to adding more!

[jpinkster]

@ryd0rz Can you open this repo up to the public so we can contribute and report issues specific to this mssql driver? Others in the community would love to help contribute to this.

Also, it would be helpful to have you and @christiaanwesterbeek collaborate as it feels like he has built the full version of this driver (SQL and Object based). The main issue as you notice in this thread is that we have a terrible work around in order to connect the driver to the base db-migrate library.

Thanks everyone!

[christiaanwesterbeek]

@ryd0rz You mean your repo for db-migrate-mssql is not public? Why would you close source that one? You're missing out on contributions by the community.

Let's work together on a single mssql driver for db-migrate that all of us can contribute to.

[wzrdtales]

Agreeing, there is no reason to close something that contributes to open source and giving back to the community.

[ryd0rz]

Hey everyone, the repo is actually public...

Here's the repo:

https://github.com/ryd0rz/db-migrate-mssql

We can work on merging any PR and I can even add you @christiaanwesterbeek as a collaborator if you'd like.