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 understand the schema set against an Entity in the designer is intended to allow you to override the default schema set on your LightSpeedContext. I am developing a new project model first, and want every class in a single (non-default) schema (in SQLServer2014 - so using the SQLServer2012 database provider). I also want to maintain my SQLServer Tables during development by using the "Update Database" option from the design surface. I've worked out that I must create my KeyTable manually to get it into my schema (as per http://www.mindscapehq.com/forums/thread/1153489 ). I've also worked out I need to set my LightSpeedContext.Schema (from that same post). I've found that to create my Tables in my new schema I need to set the Schema attribute on each LightSpeed Entity in the designer. If I don't set the Schema attributes then they are created in the default dbo schema when I take the "Update Database" option (from the designer). Question: Is there a way to set the schema used when Updating the Database from the designer (without setting it on each Entity as I am now) ? Cheers, Simon. |
|
|
No unfortunately you do need to specifically set this on each entity.
|
|