Entity Framework model-first design not won't let you edit the table mappings?

EDMX is not database agnostic. SSDL part of EDMX is tightly coupled with database server (in case of MSSQL even with its version). You need separate SSDL for each supported database server I don't understand how changing column names relates to database agnostic model.

Reverse is true! If you need your database to have different column names for different server products you need separate mapping for each of them! Changing column names when using model first is possible only if you modify T4 template used for generating database creation SQL script.

But every time you create that script designer will delete whole your storage description (SSDL) and mapping (MSL) and replace them with a new one The easiest way to have database agnostic code is using code first but even then you can have problems with some type and feature inconsistency among servers If you want database agnostic ORM you should probably check N.

EDMX is not database agnostic. SSDL part of EDMX is tightly coupled with database server (in case of MSSQL even with its version). You need separate SSDL for each supported database server.

I don't understand how changing column names relates to database agnostic model. Reverse is true! If you need your database to have different column names for different server products you need separate mapping for each of them!

Changing column names when using model first is possible only if you modify T4 template used for generating database creation SQL script. But every time you create that script designer will delete whole your storage description (SSDL) and mapping (MSL) and replace them with a new one. The easiest way to have database agnostic code is using code first but even then you can have problems with some type and feature inconsistency among servers.

If you want database agnostic ORM you should probably check N.

Yes, you're right about the database agnostic point - changing column names doesn't really have much to do with that. In fact, if you were to move a database from one vendor to another, you would probably strive to keep the table and column structure as identical as possible in the new system. Ultimately, I wanted to see if EF4.1 would have the same flexibility for mapping column names that our cumbersome homegrown system has, and my example was the closest I could think of to illustrate where that might come in handy.

I think you answered my question perfectly. Thanks! – Derek Jul 24 at 1:50.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.