Schema is important. But the real killer is the lack of normalisation in databases such as Mongo.
This is *not* a problem in a graph database like Orient because the edges can make direct links to normalised fields. In a database like Mongo you are likely to encounter all of the problems that normalisation solves: It is common for people to mistype field contents. When these are significant fields such as customer name you can believe that you are correctly accessing your information but end up either missing records or including spurious, unrelated, records. On Monday, 9 November 2015 12:39:47 UTC, scott molinari wrote: > > Ok. Just wanted to be sure. > > Also, do you agree with the point Lukas Eder was making in his article > "Stop Claiming that you’re Using a Schemaless Database"? > > I tend to disagree on the "schema is a good thing that you always want to > have" argument. He is ignoring the schema migration and code refactoring > issues present with SQL. This blog post series (also from MongoDB) makes > the issue very, very clear. > https://www.mongodb.com/blog/post/mongodb-vs-sql-day-1-2 > <https://www.mongodb.com/blog/post/mongodb-vs-sql-day-1-2> > > I agree, on the other hand, with the fact that there always needs to be a > schema. It is just a difference between the code determining the > correctness of the schema or the database imposing schema, which has to be > kept up-to-date with the code, which means "versioning" of schema, which > becomes and additional hassle for agile development. The fact ORMs are > built to make Objects match RDBMSs just goes to show the real issue. It > amazes me how controversial the discussion are about using ORMs. Everyone > who argues about the usefulness of ORMs hasn't seen the light of storing > and retrieving object state at will and what it means to the simplicity of > programming. > > Scott > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
