> 3. While upgrades aren't hard, they're not easy either. And in my experience, apart from ease of use there's also a major trust issue here. If you're upgradi

> 3. While upgrades aren't hard, they're not easy either. And in my experience, apart from ease of use there's also a major trust issue here. If you're upgrading your app server framework/language, it's easy enough to do a rollback. With databases, people are worried that they might not notice errors right away and then you have to merge the data accumulated since the upgrade with the last backup in case of a rollback. Not saying that this is entirely rational... Also, new features on the SQL level are hard to sell if all you're doing is lowest common denominator ORM ("New window functions and faster lateral joins? But we're doing all that in our code!").