3 ms·
Some good points in here about the tradeoffs you make with Couch. One I didn't quite understand: "For instance I cannot have a view that filters out fragments
by jdminhbg 16y ago
Some good points in here about the tradeoffs you make with Couch. One I didn't quite understand:
"For instance I cannot have a view that filters out fragments that have publish dates in the future."
Isn't this as simple as ?startkey=0&endkey=[now] ?
- brehaut 16y agoThat requires date information to be in the keys of all the views. Some of my views are not chronologically keyed, but i would still like them to have items that i intend to have be published in the future not accessible. I would like to avoid that sort of accidental complexity. The other issue is that it splits the 'is this a visible fragment' logic across the db and application code boundary. I now have to ensure that all the appropriate checks are in place in two layers rather than one.
- swannodette 16y agoisn't this the kind of thing that filtered replication is designed to handle?
- brehaut 16y agoI've not looked into that at all. Thanks for the pointer