Feat: MsSql support#1610
Conversation
|
@Angelelz I guess we should not include RQB in first iteration for MSSQL. So it can be another PR scope, same as |
|
Hello, Thank you for the time you devote to this dialect. I can not wait to see him :) |
|
No idea why the tests are not passing. They run well locally. Any idea @dankochetov ? |
|
Some features have been postponed to later PRs, the scope of this one is already huge as it is.
|
…ql does that for us
|
The PR has been updated to resolve conflicts and use the new structures/features of the library. |
|
Is no one going to respond to @Angelelz? next steps are needed. |
In my opinion, they are waiting, hoping that a sponsor might come forward. Right now, it’s not profitable for them. |
|
Just to put this out there. This is a 40k+ line PR, and this is only half of what is needed to support mssql. The team will do its best but remember that drizzle-kit support will be needed before this is merged. This PR is only for the ORM side. Mssql requires new syntax to introspect, generate migrations, support the studio, and other drizzle-kit stuff. My understanding is that the team will take care of that part. |
great, thanks a lot for all this effort it would be great to have an issue with the remaining tasks, so we can track it, and it would help everybody understand what's still missing |
|
Any progress on this? |
Removed: - smalldate and mediumint columns Added: - snake_case and camelCase to config Updated: - table config and some columns configs. No need to pass names to columns - View config
Fixed dprint issues Commented mssql dialect in drizzle-kit
Updated: - tests (added names to constraints) - made constraint names mandatory for mssql > Mssql generates names with custom hash - top, offset and fetch are now accept placeholder Added: - drizzle mock - new tests for top, offset and fetch Also commented mssql logic in drizzle-kit as it is not supported yet
…to feat-mssql-support
| console.log(wrapParam('host', options.host)); | ||
| console.log(wrapParam('port', options.port, true)); | ||
| console.log(wrapParam('user', options.user, true)); | ||
| console.log(wrapParam('password', options.password, true, 'secret')); |
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
|
|
||
| statement += it.generated | ||
| ? `.generatedAlwaysAs(sql\`${ | ||
| it.generated.as.replace( |
Check failure
Code scanning / CodeQL
Incomplete string escaping or encoding High
| statement += `\n\t`; | ||
| statement += 'check('; | ||
| statement += `"${it.name}", `; | ||
| statement += `sql\`${it.value.replace(/`/g, '\\`')}\`)`; |
Check failure
Code scanning / CodeQL
Incomplete string escaping or encoding High
…to feat-mssql-support
Updated tests
…to feat-mssql-support
@Angelelz wondering if you saw this? I think they want more visibility on this, I know that would certainly get more eyes on it at least. (and make it easier to delegate remaining work for anyone who want's to also help). |
|
Can't wait to use this! |
|
Can we please merge this? 🙏🏻 we have all been waiting a long time for this fix. What is blocking it? |
|
@AndriiSherman any news on mssql? ❤️ |
|
There is a new version of node-mssql 12.0.0, will it be compatible? |
This PR aims to close #585.
The initial implementation and the first couple of tests are implemented. I will update this description with the status of the implementation.
Initially the only supported driver will be
node-mssql.There is still a lot to do:
Mergesupport (to do upsert type of functionality)$onUpdate