4 ms·
> To allow others to impl the data store they want and to avoid having to write blog posts like these. But why? For the longest time MySQL didn't support wind
by jimktrains2 9y ago
> To allow others to impl the data store they want and to avoid having to write blog posts like these.
But why?
For the longest time MySQL didn't support window function or CTEs. What do you do if you're using those? (I'm not sure of SQLite's window support, but I'm pretty sure it has CTEs.)
If you're using postgres, should you not use pg_trgm (trigram indexer to use an index for regex searches on text), postgis (GIS tools), pg-routing (routing tools), ossp_uuid (uuid support), better types (boolean, range, inet, geometric, &c), or features such as RETURNING just because someone doesn't like my choice of database? No, I'm going to do what makes my life easier and my application faster and more featureful.
- kodablah 9y agoI think your talking about SQL abstraction and I'm talking about persistence abstraction. I would never consider sharing SQL across vendors.
- jimktrains2 9y agoThe way you persist has consequences to what types of features you'll build, and it'll end up being the least common denominator, not allowing you to use any advanced or efficient features of your store.