I think the orm should include mssql as a supported database type by default instead of doing a custom database setup
there is some WIP here:
https://github.com/UTGuy/mikro-orm-mssql
Going forward I'd like to support it natively, although not a priority.
there is some WIP here:
https://github.com/UTGuy/mikro-orm-mssql
Going forward I'd like to support it natively, although not a priority.
I am actually starting out a new project in about two weeks later which is on mssql and wanted to use mikroorm instead of sequelize but I am not only the sole developer in the project so we are looking for sequelize alternative which supports mssql out of the box
Will try to spend few hours to check how much is actually done and what is the needed effort to support it.
@B4nan any updates
I must say SQL server has very weird limitations. First I hit the issue with composite FKs that are sometimes impossible to create in a lazy manner due to SQL server trying to be too smart/strict (it does not allow setting cascading). Now I see Cannot insert explicit value for identity column in table 'book_tag2' when IDENTITY_INSERT is set to OFF. 馃し
Why are people using this? :P Seriously, go with postgres people :P
Anyway, I have around 2/3 tests passing, disabled FKs in the schema generator for now, I know what to do to make it work (and it will also allow having FKs in sqlite at least for creating new tables). So still not there, still few days/weeks ahead of me.
yes, Sql server is too smartass .I came up with those problems when i migrated from pg to mssql
Most helpful comment
there is some WIP here:
https://github.com/UTGuy/mikro-orm-mssql
Going forward I'd like to support it natively, although not a priority.