Databases always have a schema (2018)

Re:Databases always have a schema (2018) by hombre_fatal on Monday February 25, 2019 @01:01PM (#19247734)

One problem I had at jobs that used Mongo was that any other tools/systems that connected to the database had to be synchronized as well. It's not enough that this one system enforces a schema.

Classic example being that our code used visibility_score but a tool was adding a visibilityScore property to every document as part of a cron job calculation.

[ Parent | on HN ]

Re:Databases always have a schema (2018) by scarface74 on Tuesday February 26, 2019 @08:18AM (#19253990)

That comes down to organizational standards. When I worked with Mongo, all of the code was done in C# and the POCOs were in a shared internal Nuget package. There was never any harm in using older POCOs. You can add a catchall property to the POCOs that round trip any fields that it doesn’t know about.

[ Parent | on HN ]