There is nothing new here. A DBA does not like that a database is subjectively misused, and then gets pissy and arrogant about it. E.g., "You’re just being lazy or scared of SQL." I'm not a fan or O/R-Ms myself but I do not feel compelled to shout it from the rooftops. shrug
Yeah... I am on the same side of the fence as the author but I've also had very little success at evangelizing SQL and stored procedures to OO devs, so I've pretty much stopped.
One point that I do think makes sense is where he says "just use flat files". Not that I'd actually advocate that, but if you're going to completely paper over the set-oriented nature of your data store, why not use a "NoSQL" (key/value) database and be done with it.
Comments
There is nothing new here. A DBA does not like that a database is subjectively misused, and then gets pissy and arrogant about it. E.g., "You’re just being lazy or scared of SQL." I'm not a fan or O/R-Ms myself but I do not feel compelled to shout it from the rooftops. shrug
Yeah... I am on the same side of the fence as the author but I've also had very little success at evangelizing SQL and stored procedures to OO devs, so I've pretty much stopped.
One point that I do think makes sense is where he says "just use flat files". Not that I'd actually advocate that, but if you're going to completely paper over the set-oriented nature of your data store, why not use a "NoSQL" (key/value) database and be done with it.