My previous post got referenced in the CouchBase newsletter, and I’m really glad it did because while I came up with what I thought was a clever solution it was also wrong. (D’OH!)
The issue I didn’t consider that some kind commenters on the previous post pointed out is that my approach creates side effects because I’m emitting documents in the view based on information that isn’t in the document itself. Specifically since I’m using the current system date/time when the view is created, the documents included in the view will be ones for which the criteria is valid when the view is created.
What this means is that although views get updated with current data as data within documents changes, since the entire view isn’t generated each time the criteria used to determine whether or not documents are included in the view is a fixed point in time. To put it another way, my current system date/time that was current when the view was first created essentially becomes hard-coded once the view is created, which isn’t at all what I needed. This causes issues if the start and end date properties in the documents change after they’ve been added to the view because the view only checked to see if the date criteria was met at the time the document was added to the view.
There are some great suggestions in the comments on my previous post for including data in the document itself that would allow only valid documents to be pulled right from Couch, and you’ll certainly want to check those out if you’re dealing with a ton of data. The solution I’m using will not be ideal for massive datasets but since that isn’t the situation I’m in with this data, I wanted to share the solution I came up with in case this works for other people.
To describe my documents again, I have documents that need to be displayed on a web page if their start date/time property is less than the current date/time and if their end date/time property is greater than the current date/time.
Since the valid ranges go in opposite directions for those fields, I didn’t see a way to do something like have an array key that included both the start and end dates that would allow me to get only the documents I want back from Couch. But what I can do is use a single document property as a key in Couch and get close to what I want, and then I can pare the documents down further in the application code.
In my case the end date is a more strong limiting criteria since over time there will be a large number of documents with both start and end dates in the past, but documents with end dates >= the current date will be much fewer in number (only a handful in the case of this specific data).
With the end date/time as the key, on the application side I can simply use the current date/time as my start key when I call this view, and that gives me all documents with a valid end date/time (>= current date/time).
At this point I may still have documents that shouldn’t be displayed based on the start date/time, however, since when people enter data into this application they can schedule things for future display (i.e. both start and end date/time are in the future). But, again since I’m not dealing with a huge amount of data once I limit by the end date/time, it’s simply a matter of looping over the documents I get back from Couch and checking for a valid start date/time (<= current date/time) and only displaying those documents.
The issue my original view code created makes total sense now, so thanks to the commenters on my previous post who pointed out the fatal flaw in my approach. Nothing like doing something wrong as a means of learning.