3 ms·
> This blog post is calling at least two different things SQL, and it's kind of infuriating. For better or worse, that's not what "NoSQL" means. I understand t
by CharlesW 6y ago
> This blog post is calling at least two different things SQL, and it's kind of infuriating.
For better or worse, that's not what "NoSQL" means. I understand that the name is a bit infuriating, and I personally map it to "non-relational" as I read.
> What's gone away is the practice of writing complex, highly linked, normalized database schemas with layers of constraints and foreign key references.
This may be true for some use cases, but in general that's wishful thinking.
- jolux 6y agoThere still seems to be a decreasing amount of appreciation for the relational model and the power of SQL databases to maintain data integrity. I'm not quite sure why because relational databases are a uniquely powerful tool in software engineering.
- CaptainZapp 6y ago> This may be true for some use cases, but in general that's wishful thinking. Why would avoiding implementation of database level constraints be "wishful thinking"? Au contraire: I strongly believe that data level constraints should be tied to the database. Sure, there's a trade off between indexing, constraints and performance. But I rather have an additional unique index on a column than relying on the fact that all developers in an organization always do the right thing. If the database is my responsibility then I'll make damn sure that it's not possible to fuck it up with shlocky code.