Case Sensitivity for ORM?

Case sensitivity for ORM? Why? The standard for SQL says that table names, column names, etc. are all case-insensitive (in spite of earlier versions of MySQL). My friend from San Antonio, Doug Boude had this and more to say about his experiences with ORM:

The first reason my ORM gave me to hate it was that it forced me to have to synchronize case between field names and elements within different XML files. Coldfusion has LONG been a case-insensitive language for the most part, but suddenly now, as I am embarking on a journey through the foreignness of ORMs, I have to ALSO be mindful that everytime I type in a field name, I had just BETTER make sure I type it exactly the same way every time! Of course, I learned about this the hard way, through many hours of troubleshooting, following nearly useless error messages, and piecing together scraps and tidbits from here and there on the net building myself a "Franken-Solution".

Aha! Hmm... in particular, the phrase "following nearly useless error messages" sounds really familiar... hmmmm... oh wait, I know, I mentioned that about case-sensitivity in general in one of my own blogs. And I'd be willing to bet, the reason why it was an issue at all is because they chose an ORM tool written in Java rather than one purely in CFML... which speaks yet again to that notion of moving data from a case-insensitive language to one that is case-sensitive (i.e. "stupid"). Trying to configure an ORM if case-sensitive with CFML instead of XML (think ColdBox handlers), would be a nightmare because of the same SerializeJSON problem!

And after all that headache, what value is added to this ORM by its being case-sensitive? Zip, zilch, the big nada, via con dios mi amigo! Just another example of programmers often preferring something that's objectively worse than the alternative because they have warm fuzzy feelings about their past decisions.