Re: Repeat: there's no standard SQL implementation...
Indeed.
"and a well-behaving application shouldn't really care which SQL database engine it's talking to as long as it follows the standard."
Well, sure, if you go with the DHH thing about avoiding stored procedures. If you have umpteen lines of T-SQL or PL/SQL or Pg/Sql, life could be a bit harder. Pure SQL is fine for specifying states, but one usually needs to enforce rules about the transition between states, and when it gets procedural, each vendor does that its own way.
Biting the hand that feeds IT
