couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From svilen>
Subject Re: Mass updates
Date Thu, 09 May 2013 12:52:52 GMT
> >>>> The main concern I have is maintaining a consistent state across
> >>>> code releases.  Presumably, our data model will change over the
> >>>> course of time, and when it does, we need to make the several
> >>>> million old documents conform to the new model.

a question: do u need to keep the old variant/state too? 
(think bi-temporal stuff)

that one, and if the once-off conversion process is going to take
loooong time, it might be better to bite the bullet and allow for
multiple (e.g. 2) versions of the "schema" to coexist - in both
server/views and client code. Thus once u already have some doc in the
new variant, use it. Else, fallback to runtime-conversion.

i know it isn't easy to organise but otherwise u're fighting reality.


View raw message