4 ms·
> You can simulate noSQL with graph and RDBMS tools - but, again, you shouldn't What is the feature which makes the noSQL which you shouldn't do in a relationa
by johannes1234321 4y ago
> You can simulate noSQL with graph and RDBMS tools - but, again, you shouldn't
What is the feature which makes the noSQL which you shouldn't do in a relational database? To me noSQL always looks like a subset of relational database. The only thing, maybe, is that you can truly put everything in, but with modern JSON features and all the other things I don't see a downside in using relational. (Except a little learning curve, while that can be hidden behind some ORM or something if you really want for the beginning)
- warrenm 4y agoThe "schema on the fly" is the draw for noSQL - nothing has to be rigidly predefined like an RDBMS mandates
- johannes1234321 4y agoCREATE TABLE foo (doc JSON); done. If that's really what you want.
- warrenm 4y agoFor every bit of JSON that comes in? No And then having to figure out what all the fields are after the fact? No That's why noSQL exists
- johannes1234321 4y agoWhat is the thin noSQL brings to the table which a relational system doesn't have? (Except that writing a depth search in a JSON document in SQL is a bit more cumbersome, but if that is a concern that can be wrapped in a data access library to generate the SQL)
- warrenm 4y agoI think I've explained that above - it's not having to be rigidly tied to a schema :)
- johannes1234321 4y agoNot that my "schema" is really rigid ... just a little more convoluted syntax than "createCollection" but underneath quite similar.