MongoDB queries don’t always return all matching documents

Re:MongoDB queries don’t always return all matching documents by catnaroek on Tuesday June 07, 2016 @08:10PM (#11859078)

Exactly. While the process of designing the structure of your data can make you feel like “you're not getting real work done”, in the long run, it actually prevents headaches caused by inconsistent data. Data always has a structure, it's just that some people are too lazy or mentally feeble to figure out what it is.

[ Parent | on HN ]

Re:MongoDB queries don’t always return all matching documents by collyw on Wednesday June 08, 2016 @03:42AM (#11860659)

For me that is the most important aspect of starting / designing an application. If the data model is accurate, then the code falls into place easily. If its not quite right, more and more code ends up in the application trying to make up for the poor data model.

[ Parent | on HN ]

Re:MongoDB queries don’t always return all matching documents by varunom on Wednesday June 08, 2016 @07:24AM (#11861462)

I second this.

My first task in any project is to design the whole data model based on current requirements and while designing it I think of the interfaces and how would they read and write data (to refine requirements). Writing views and actions/APIs on top of well-formed data model then becomes a breeze.

[ Parent | on HN ]

Re:MongoDB queries don’t always return all matching documents by collyw on Wednesday June 08, 2016 @08:54AM (#11861890)

Its so un-agile (but it works).

[ Parent | on HN ]

Re:MongoDB queries don’t always return all matching documents by nathan_long on Thursday June 09, 2016 @02:34PM (#11871366)

Agile doesn't mean "don't gather requirements or plan anything." It just means that you evaluate your results frequently and maybe change course, instead of waiting until the end when you're "done".

[ Parent | on HN ]