Support for MS SQL

[juliano]

Fixes #451

Problem

Quill doesn't support MS SQL Server. This PR adds this support.

Solution

Implemented Sql Server context and dialect

Notes

As suggested by @gustavoamigo I put this code in a different project in order to not mess up with the current build or make it slower, once that I need a different docker image to do the setup. To set up the entire environment just run:

docker-compose stop && docker-compose rm && docker-compose run --rm setup && docker-compose run --rm setup-sqlserver

I am not entirely sure if this is the way to go, any suggestion here would be great.

Checklist

• Unit test all changes
• Update README.md if applicable
• Add [WIP] to the pull request title if it's work in progress
• Squash commits that aren't meaningful changes
• Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

[mxl]

Nice! But should not we keep all jdbc related stuff in quill-jdbc project? (See #665)

[mosyp]

@getquill/maintainers We should definitely split jdbc module to different artifacts, as with async modules. Ideally, move quill-jdbc drivers/implementations to different repository

[juliano]

So, do we have a consensus? Can we go with a different project?

[fwbrasil]

@juliano Sorry for the late feeback. I'd prefer to keep all jdbc integration under quill-jdbc since Quill doesn't depend directly on any specific driver, except for tests, and the jdbc api is pretty stable.

[juliano]

@fwbrasil sounds good to me. I'll change the test containers and put everything under quill-jdbc

[fwbrasil]

@juliano any updates on the changes?

[juliano]

@fwbrasil not yet because I am on holidays, I will be back in 10 days :)

[fwbrasil]

@juliano enjoy! :)

[mxl]

Please use debian:jessie image because all other containers are using it or better move mssql setup to setup container. Unfortunately official mssql container is available only as Ubuntu and RHEL based so this will be the only exception.

[juliano]

I will update that! 👍

[mxl]

@juliano We are solved issue with long running build by parallelizing Scala 2.11 and 2.12 builds. Also there are other possibilities to parallelize build, e.g. to build each module in separate job.
I thought about splitting this repository into separate repositories for each module as @mentegy suggested but this will create many maintaining problems and mess which we will not able to handle.

[kentongray]

WOW! @juliano you are my hero

[juliano]

@kentongray I am glad to help! :)

@mxl it's almost there, but it seems I need some help :/

[mxl]

@juliano I'm here or ping me in Gitter.

[mxl]

@juliano Problem solved in #784

[juliano]

@mxl it seems it didn't worked :/
Can you please check if the problem is still the same?

[mxl]

@juliano For some reason it fails when connecting to MS SQL Server because database was damaged(?):

Sql Server ready
Msg 922, Level 14, State 1, Server 8eedbd6c1d56, Line 1
Database 'model' is being recovered. Waiting until recovery is finished.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Cannot open database "quill_test" requested by the login. The login failed..
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'sa'..

[mxl]

No need in nb_NO.UTF-8 locale and tzdata reconfiguration (see http://stackoverflow.com/a/38553499/746347)

[mxl]

en_US.UTF-8 should be here.

[juliano]

Finally!

[kentongray]

awesome! not to pester and I'll patiently wait but I'm eager to try this out, will this be auto published as a snapshot or will I need to wait till the next release?

[mosyp]

@kentongray each successful build in master is published as a snapshot to sonatype :)

[kentongray]

Just letting you know I tested the ms sql support and initial tests were super promising! Love this lib! Thanks everyone