-
-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The same Table name on different schemas on MSSQL #631
Comments
I am not currently having this issue, but looked around because we do have lots of schemas and the possibility of overlap in the future is not vanishing. Since there doesn't seem to be anything baked in, I suspect that you could roll-your-own with the |
When using the sequelize-auto command to create the objects from the Databank and there's a Table name doubled in different schemas like dbo.dataStatus and example.dataStatus, the generator first creates the dbo one and then override it with the one from the cloud. So my Question is, if there is a way, to let the generator write the schema in the object name. So instead overriding dataSatus create for example dbo_dataStatus and cloud_dataStatus?
The text was updated successfully, but these errors were encountered: