Hi all,
Looked through the major philosophie changes of ODK v1.x and v2.0. Looks
great!! Will there be any such high level changes in the approach to form
versions? In other words, currently, for text mods, fine, just a version
increment. If you change structure (add, substract a var, a list of choice
options, etc.) you have a new form and collection database and it is up to
the project team to reconcile the two data sets coming from the two
versions. Will there be any modifications big or small to this "modified
form" approach? For example just adding a new var or new option choice
doesn't seem to engender db problems, just that there would be holes (null
values) in the data export from previous versions.
Thanks,
Curtis
At present, no; the adding of a field to a table would necessitate a new
storage table.
ยทยทยท
On Wed, Aug 10, 2016 at 2:51 AM, Curtis Broderick <c.broderick@epiconcept.fr wrote:Hi all,
Looked through the major philosophie changes of ODK v1.x and v2.0. Looks
great!! Will there be any such high level changes in the approach to form
versions? In other words, currently, for text mods, fine, just a version
increment. If you change structure (add, substract a var, a list of choice
options, etc.) you have a new form and collection database and it is up to
the project team to reconcile the two data sets coming from the two
versions. Will there be any modifications big or small to this "modified
form" approach? For example just adding a new var or new option choice
doesn't seem to engender db problems, just that there would be holes (null
values) in the data export from previous versions.
Thanks,
Curtis--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com