Any chance to get an update that prefixes the model names with the schema and then generates classes that adhere to that name?
So that [Stg].[Trade] turns into - as namespaces are ignored in entity framework - the StgTrade class?
I have a couple of larger projects that are fighting to be used in Entity Framework because an old pattern is that every subsystem has unique table names within it's subsystem, and the subsystem is a schema. In the above example I have [Trade] in [trd],[sim] and [simstg] (Trading, Simulation and Simulation-Staging) and thus can not use Entity Framework at all. Multiple similar applications here.
Manipulating the code generation is not good enough - that has to come, at least as an option - from the tool support. We use Model FIrst for the obvious reason that there is no proper schema support in Entity Framework - not when you REALLY use SQL Server (partitioning, compression, filtered indices and all that).
So that [Stg].[Trade] turns into - as namespaces are ignored in entity framework - the StgTrade class?
I have a couple of larger projects that are fighting to be used in Entity Framework because an old pattern is that every subsystem has unique table names within it's subsystem, and the subsystem is a schema. In the above example I have [Trade] in [trd],[sim] and [simstg] (Trading, Simulation and Simulation-Staging) and thus can not use Entity Framework at all. Multiple similar applications here.
Manipulating the code generation is not good enough - that has to come, at least as an option - from the tool support. We use Model FIrst for the obvious reason that there is no proper schema support in Entity Framework - not when you REALLY use SQL Server (partitioning, compression, filtered indices and all that).