> SQL transaction model doesn't make a lot of sense .... anything that uses the internet
So decades of PHP+MySQL and Rails+PostgreSQL were simply misguided?
So decades of PHP+MySQL and Rails+PostgreSQL were simply misguided?
To the extent that transactions were the point, yes (though there may not have been many alternatvies for a datastore to use when Rails was getting started).
In the case of PHP+MySQL of course MySQL transactions were disabled by default in that era (up until 2010 in fact).
After all, what do you do when a transaction fails? Most webapps either retry or fail (if they even bother to handle that case at all), but you don't need transactions to do either of those. In an actual database application you can tell the user their transaction didn't commit and ask them to deal with it, but again you can't really do that over the HTTP request/response cycle (because what if the user submits the form and walks away? They expect their input to be saved, whatever happens on your backend).