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
However, SQLConnector does not specify any schema in the SQL statements that it builds, even though there is a schema method that properly determines which schema to use for a given model.
We should use this schema method to always specify the schema in generated SQL.
@raymondfeng@bajtos What are the chances of this being implemented and released as version 3? It doesn't look like a complicated change, so I could probably implement it myself and submit a PR, if that increases the chances.
Are there any problems you can see with making this change? I know this would break loopback-connector-db2 since it needlessly overrides the schema method with a schema string property in the constructor, which is why I believe it should be released in the next major version.
Thanks :)
The text was updated successfully, but these errors were encountered:
Hi @zenflow, sorry for the delay. I am not very familiar with this aspect of connectors, but your proposal looks good to me in principle. To prevent breaking changes, perhaps we could add a new datasource setting to enable this new behaviour?
It would be great if you could contribute this change yourself!
We are working with a legacy database that has our data divided among different schemas.
As per the documentation, I should be able to set the schema for an individual model.
https://docs.strongloop.com/display/public/LB/Model+definition+JSON+file#ModeldefinitionJSONfile-Datasource-specificoptions
However,
SQLConnector
does not specify any schema in the SQL statements that it builds, even though there is aschema
method that properly determines which schema to use for a given model.We should use this
schema
method to always specify the schema in generated SQL.@raymondfeng @bajtos What are the chances of this being implemented and released as version 3? It doesn't look like a complicated change, so I could probably implement it myself and submit a PR, if that increases the chances.
Are there any problems you can see with making this change? I know this would break loopback-connector-db2 since it needlessly overrides the
schema
method with aschema
string property in the constructor, which is why I believe it should be released in the next major version.Thanks :)
The text was updated successfully, but these errors were encountered: