In contrast to client-side JS in case of SQL, there are at least some cases where limiting oneself to a single target can make sense. Not every application need

In contrast to client-side JS in case of SQL, there are at least some cases where limiting oneself to a single target can make sense. Not every application needs to run on a pletora of different databases. In addition, over time, the official SQL standard got better and better (quite unlike EcmaScript which took a 10 year break and then returned with minimal improvements) and the databases began following the standard more and more as being standards compliant became a selling feature (which is also quite unlike the ecmascript case where not even the innovative browsers support all of the new features from ES5) Hence, I would claim that the need for an SQL abstraction layer is way smaller than it is for client-side JS