-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
SQL Server: Support explicit table schema prefix in queries #154
Comments
The same issue as #89 |
Thanks for checking my ticket. Yes, it is the same root issue. It is a bit more severe for SQL Server since the work around via connection URL is not working. Its not supported by SQL Server. |
@vincentlauvlwj EDIT |
@hangingman Yes, will be a core feature. |
Supported in Ktorm 3.1.0 |
Hi.
We have an issue when using Ktorm with SQL Server. The queries do not work with a db user which has no default schema, since the schema defined in the connection (e.g. via spring data source) is ignored / not supported by the SQL server driver.
It would be good to be able to enforce a schema prefix in the queries / pass a schema in the entity definition.
E.g.
It seems this is not possible right now. Is there a suggested work around?
The text was updated successfully, but these errors were encountered: