5 ms·
Great, so force SQL to 'join' things that aren't tables and 'select' things that aren't rows. SQL wasn't built for querying every possible data store.
by scoom 8y ago
Great, so force SQL to 'join' things that aren't tables and 'select' things that aren't rows.
SQL wasn't built for querying every possible data store.
- kevsim 8y agoYeah, that was my reaction as well. I fully understand his point regarding ORMs that are meant to be an abstraction over a relational database, but imposing the relational model over non-relational datastores sounds like a disaster.
- threeseed 8y agoIf only there was a popular example of this. Wait there is: PostgreSQL. They bastardised SQL to support JSON data types just like every other vendor has to do because SQL is for relational and only relational data stores. Is this the utopia that the author is after ? https://www.postgresql.org/docs/9.0/static/hstore.html https://www.postgresql.org/docs/9.0/static/hstore.html
- oulu2006 8y agoI thought they were, for the most part, fairly logical extensions to SQL. You don't have to use the JSON/JSONB column types, they are optional. We use them extensively in production and haven't had much difficulty learning them.