[buro9]

Oh it's fine for those whose schemas fit into the type that the ORM can generate, I have no issue with the functionality existing at all. For many databases this actually is all that will ever be needed.

But for legacy databases, for the edge cases where the schema is designed for a very specific purpose that doesn't neatly fit what the ORM would generate, and especially when external applications may also call the database... I like to know that the database is exactly what I expect it to be.

[meaty]

I have a 2000 table, 45000 sproc legacy database on my hands. 20 mins to deploy the schema. Its what we expect but the maintenance cost is extreme, its not testable.

That's where the ORM comes in for legacy stuff. We're moving the schema slowly into the ORM.