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
|
Hi all! I'm using a LightSpeed with Oracle. And I have the following LS model (included in attach). All the entities except "BranchDbModel" are in the "Orion" schema. And the "BranchDbModel" is a table in the "AltairSettings" schema. I granted select and references on this table to Orion user. After I have added a "BranchDbModel" with "AltairSettings" specified in the Entity's Schema attribute I was unable to update source or database in the designer. Designer is hanging a little and doing nothing. How can I solve it? |
|
|
|
|
I'd like to add that at the runtime I was managed to make selects using uow.BranchDbModels which is mapped to this table from extern schema. |
|
|
|
|
While this is supported at runtime the designer requires all of the entities on a given model to be of the same schema with the Oracle9 provider. The approach to take here is to have a separate designer model per schema.
|
|
|
|
|
Thank you, Jeremy, for your answer! So, is there any way to make an association (one-to-many for example) between two different schemas (located in separated designer models)? It's because I have a list of Branches in schema1 but in schema2 I have some entities that are associated with Branches (they are referencing to Branches using BranchId field). |
|
|
|
|
Yes you should be able to do this using a linked model, see http://www.mindscapehq.com/documentation/lightspeed/Working-with-Models-in-the-Visual-Designer/Linked-Models for details about setting this up in the designer. Im not 100% certain but Im fairly sure this should avoid the schema issue you are seeing when trying to import the entities directly as the linked entities are ignored for code generation purposes which is where the original error is being triggered.
|
|
|
|
|
Dear Jeremy, I tried to use a Linked Models and found some bugs. I captured a small video about it. Please, have a look here: http://www.youtube.com/watch?v=VXHiUyr1pW4 I note that this feature (linked models) is working in a half. Could you please improve it? |
|
|
|
|
Uploaded here this test solution. |
|
|
|
|
Thanks for the detail on this - you are specifying two different connection strings (one for each model) but providing linkages between the models so this will likely be the cause of the issue as we expect the same connection to be used for any linked models. I will have a look to see if this is the case and surface an error message rather than it silently failing.
|
|
|
|
