Resolving naming convention conflict between entities in EF4 and our database standards?

Question

I\'m investigating replacing or supplementing our home grown ORM system with the Entity Framework 4, and I\'m noticing that the latter may end up causing a conflict between

Answer 1

The correct solution is to change your database naming convention.

Why should the tail wag the dog? In modern programming most of the action takes place in the highly scalable business/service layer, not the database. Programmers should use a naming convention that works for both - and it should cater to the needs of the application developer who is going to be working with these objects day in and day out. In some cases it should probably cater to the needs of the front end developer, in others the server side.

The whole purpose of a naming convention is to reduce complexity. Yet the accepted solution here is to implement all kinds of additional complexity. And every other ORM would have to come up with their own convoluted solution to this artificial problem.