Hello,
In our situation, each EntityContainer maps to exactly 1 schema. A table with the same name _might_ occur in multiple schema's, but until now me managed to avoid this.
I'll try to give a more practical example of what we try to do.
Imagine a car dealership. The database contains information about customers, car configurations and car orders placed by customers. So, to keep things organized, this can be split up into three schema's within a single database instance:
* customer: Contains all tables which relate to customer accounts, addresses, ...
* configuration: Contains all tables which relate to car configurations and car options. (What's possible on which make and model.)
* orders: Contains all actual orders placed by customers.
Code-wise the same setup has been created: three DAL projects, each representing a single schema.
As long as I test within a single schema, Effort works fine, but when I'd place an order, thus touching more than one schema, Effort fails.
Comments: Hello, I have a similar situation , but I am working in the cloud, across multiple deployments. At this point in time, each deployment has the exact same schema, and all I have to do is change a couple of items that are passed to an EntityConnectionBuilder, and I can create a fake connection to whichever deployment that I want. My problem then becomes an issue with the System.Data.Entity.Infrastructure.DbUpdateException. Specifically (several levels deep): "__Method not found: 'Void System.Data.Entity.Core.Common.DbCommandDefinition..ctor(System.Data.Common.DbCommand)'.__". This is rather time sensitive, so any help would be greatly appreciated
In our situation, each EntityContainer maps to exactly 1 schema. A table with the same name _might_ occur in multiple schema's, but until now me managed to avoid this.
I'll try to give a more practical example of what we try to do.
Imagine a car dealership. The database contains information about customers, car configurations and car orders placed by customers. So, to keep things organized, this can be split up into three schema's within a single database instance:
* customer: Contains all tables which relate to customer accounts, addresses, ...
* configuration: Contains all tables which relate to car configurations and car options. (What's possible on which make and model.)
* orders: Contains all actual orders placed by customers.
Code-wise the same setup has been created: three DAL projects, each representing a single schema.
As long as I test within a single schema, Effort works fine, but when I'd place an order, thus touching more than one schema, Effort fails.
Comments: Hello, I have a similar situation , but I am working in the cloud, across multiple deployments. At this point in time, each deployment has the exact same schema, and all I have to do is change a couple of items that are passed to an EntityConnectionBuilder, and I can create a fake connection to whichever deployment that I want. My problem then becomes an issue with the System.Data.Entity.Infrastructure.DbUpdateException. Specifically (several levels deep): "__Method not found: 'Void System.Data.Entity.Core.Common.DbCommandDefinition..ctor(System.Data.Common.DbCommand)'.__". This is rather time sensitive, so any help would be greatly appreciated
