This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello Support, I have my model first LightSpeed tables in their own custom (non-dbo) schema in MS SQL 2014. I used the hand-created KeyTable technique to create my KeyTable in this schema too. I might in the future want to have more than one LightSpeed model in this database (eg. framework code - unrelated to the business entities, but part of the same application), which should be possible as long as each model / codebase has its own schema with its own KeyTable. Looking at the DBVersion table - I see that it can not be created in its own schema (or have I missed something?). So that means one version number for my LightSpeed models ? Do you have a recommendation on how I should handle multiple model migrations in this scenario ? Cheers, Simon. |
|
|
We dont support this as such but we dont create the DBVersion with a specific schema so the schema is driven by the default schema for the user or as defined as part of the connection string so you could try running the migrations with a connection string specifying a schema per model or connecting with independent users which drive the default schema for the connection.
|
|