You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a sequelize data model that works fine in mysql but when I switched to mssql results in errors when it tries to insert records with associations defined.
But the following sql insert statements are generated for mssql which would result in error "Error converting data type nvarchar to bigint" because it's trying to insert the uuid string into the bigint foreign key field.
A few questions:
a. Is this a bug in Sequelize ?
b. Do later versions of Sequelize e.g. v5.x or later have the same problem or is it already fixed in later versions ?
c. If no fixes are available, any recommended workaround ?
The text was updated successfully, but these errors were encountered:
Please use Github Issue Tracker only for reporting bugs, requesting new features or discussions. Ask questions on Stackoverflow sequelize.js tag or Slack. While I would like to help answer any questions but it still take too much time.
If you are reporting a bug please isolate it as SSCCE, present it nicely and follow issue template. This will help maintainers and contributors understand your issue quickly.
If you are requesting a feature spend some time to properly present your use case with some examples, current and expected outcome.
I have a sequelize data model that works fine in mysql but when I switched to mssql results in errors when it tries to insert records with associations defined.
Sequelize v4.38.0
A simplified reproduction documented below:
The following sql statements are generated for mysql which are correct
But the following sql insert statements are generated for mssql which would result in error "Error converting data type nvarchar to bigint" because it's trying to insert the uuid string into the bigint foreign key field.
A few questions:
a. Is this a bug in Sequelize ?
b. Do later versions of Sequelize e.g. v5.x or later have the same problem or is it already fixed in later versions ?
c. If no fixes are available, any recommended workaround ?
The text was updated successfully, but these errors were encountered: