I'd rather have a non-portable SQL feature than an app-level "portable" implementation that almost certainly is slower and non-transactional. Migrating to anot

I'd rather have a non-portable SQL feature than an app-level "portable" implementation that almost certainly is slower and non-transactional. Migrating to another DB will always take work, no matter how much you try to ignore flavor-specific features. Query planning, encoding and charsets, locking abilities tend to be very different. A query can run fine in MySQL and cause a deadlock in Postgres even though it's syntactically valid in both.