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. We have a business model which contains 2 schemas: dbo and extranet. We use to work with extranet as our default schema since the tables in dbo were legacy. We recently made some changes (major coupling with the legacy tables) that forced us to change the default schema to dbo. Having made this change, our integration tests started chain failing. I started investigating and noticed that every auto-through entity in the auto-generated code didn't sport the TableAttribute (thus no TableAttribute.Schema). Also, there's no way (that i found) to define the schema of an auto-through generated entity using the designer. I'm circumventing the problem by switching the auto-through to an explicit relation and specifying the schema on the generated entity. I was wondering if this is a bug, normal behaviour or if I'm not using Lightspeed in a correct manner. I'm using the 19/05/2011 nightly build. Thank you in advance, -Jonathan |
|
|
|
|
This is the expected behaviour. Auto through entities offer only the most minimal configuration options. If you want to apply options like Schema then you will need to use an explicit through entity. This is to avoid swamping the through association Properties window with entity settings. |
|
|
|
