Schemaless vs Schemaful Databases
This cluster centers on debates about the pros and cons of schemaless databases compared to traditional relational databases with explicit schemas, including challenges with schema evolution, implicit schemas, data consistency, and NoSQL advantages.
Activity Over Time
Top Contributors
Keywords
Sample Comments
How do schemaless databases make this easier?
Same. Why is having the schema in the db a bad idea?
Who said anything about db schemas? What are you talking about?
Schemas in my schema-less database? Why not just use MS SQL / Oracle / MySQL?
Why wouldn't you want your database schema to match how you use it?
If Schemaless worked on PG, would this article have seen the light of day?
Better yet in a database with consistent schema
"I don't want to create a schema..."You are always going to end up creating a schema, whether it's explicit in your tables or implicit within your code. Otherwise you end up with completely heterogeneous data which is impossible to query in any useful way.This is a red herring.
not all databases require rigid schemas. a filesystem, for instance.
thanks!i am collecting stories about problems with altering schemas while prototyping and while in production (losing data, manual altering tables, relational dbs restrictions, many-to-many relationships and other complexities) but it seems it all went smoothly with the tools you had.