You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2018. It is now read-only.
// 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.
Thank you
BR
Marco
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 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.
Thank you
BR
Marco
The text was updated successfully, but these errors were encountered: