SQL Server "User-Schema Separation" and Entity Framework issues
- by Ryan
I have been fooling around with EF with a database that has implemented user-schema separation with a twist, there are multiple tables with the same name but are separated via the schema.
So like:
admin.tasks
staff.tasks
contractor.tasks
When I created my EF model I noticed that there were 3 tasks tables:
tasks
tasks1
tasks2
Is this by design?
Also is there a way to tell EF to add the schema to the name of the entity or am I SOL and doing it myself?