// some more logic needed // what if design document exists but view doesnt, we cant just overwrite it // // we need a way to fectch and build on // and thats the reason why im not doing this at 5am
I wanted to ask whether there is any other good, production-ready example for lazy view creation.
Is it possible to efficiently detect view definition changes on lazy view creation to realize some kind of "Lazy view update"?
I am new to couchdb and nano, so I don't know yet how this could be implemented in a performant way. It would be nice to have a clean and performant example for this common task.
From the lazy view creation example code:
// some more logic needed // what if design document exists but view doesnt, we cant just overwrite it // // we need a way to fectch and build on // and thats the reason why im not doing this at 5amI wanted to ask whether there is any other good, production-ready example for lazy view creation. Is it possible to efficiently detect view definition changes on lazy view creation to realize some kind of "Lazy view update"?
I am new to couchdb and nano, so I don't know yet how this could be implemented in a performant way. It would be nice to have a clean and performant example for this common task.
Thank you
BR Marco