ODK:
Hi,
I am about to deploy Aggregate v1.0 ALPHA SIX. I'd like to know:
- How stable is it?
Do you know of any serious problems in that version? Particularly ones
that would corrupt data or cause data loss?
Thanks!
Greg
ODK:
Hi,
I am about to deploy Aggregate v1.0 ALPHA SIX. I'd like to know:
Thanks!
Greg
you should try the beta instead of the alpha. it should be more
stable. that said, we can't guarantee that the betas and alphas are
rock solid, so you should test yourself before using it in an actual
deployment.
Is the data store compatible between the two versions?
I believe the permissions table is not compatible. There may be others. We
did change how strings were stored also I can
Sorry accidently hit send... to finish
Strings also changed but I can't remember what alpha version they changed
in. Mitch would know but he probably won't be checking email until Monday.
W.r.t. alpha 6 ++ and what's different in beta rev. 2:
===============
Datastore changes:
(1) MySQL: fix to an off-by-one in interpreting the precisions of decimal
data fields from a describe on the table.
(2) Postgres: change date-time representation to use Timestamp to support
dateTime and time fields.
(3) Google AppEngine: change decimal (fractional) data to be stored as
Double (had been string).
(4) all platforms: _registered_users table schema change
-- drop this table when migrating to have it recreated (you'll need to
re-enter the registered users).
Of these, (3) is an incompatible datastore change affecting form data. (3)
and (1) cause problems with decimal data storage. If you don't have decimal
values in your forms (i.e., if you just have integers and strings), you
should be OK. Because of (3), I would definitely upgrade to beta rev 2 if
you are deploying to GAE.
============
Other changes:
(1) external publication of data to fusion tables and rhiza insight was
changed to use POST requests, allowing for very wide tables to be
published. Before, data was sent on the URL string, and that hit the URL
max length constraint after a few dozen columns.
(2) dateTime and time formatters were added. Previously, only date
formatters were defined, so if you had a time or dateTime value (new to
1.1.6 and 1.1.7), you couldn't see the time, only the date. Submission date
metadata is now formatted as a dateTime.
(3) more date formats are properly recognized in a submitted form field.
(4) support field names with a wider variety of Unicode letters
(internationalization issue).
(5) numerous fixes for Unicode character presentation and processing issues
on webpages.
(6) fixes for Unicode characters showing correctly in Briefcase downloads
from datastore.
(7) support for purging already sent to an external service and deleting
configured external services.
(8) fixes for SSL submissions to aggregate from ODK Collect 1.1.6 and
1.1.7.
Alpha 6 ++ supported authenticated submissions, but not submissions over
https.
(9) fixes for securing the website so as to require https when accessing the
website.
(10) changing the super-user in the configuration file and redeploying did
not purge
the old super-user accesses from the grants table.
(11) new UI, with scaled-down-image previewer.
(12) GAE: Fix various issues causing filters and comparisons to fail (e.g.,
with null values and alternate numeric types)
Mitch
On Thu, Jun 16, 2011 at 10:41 AM, W. Brunette wbrunette@gmail.com wrote:
Sorry accidently hit send... to finish
Strings also changed but I can't remember what alpha version they changed
in. Mitch would know but he probably won't be checking email until Monday.
On Jun 16, 2011 10:39 AM, "W. Brunette" wbrunette@gmail.com wrote:I believe the permissions table is not compatible. There may be others.
We
did change how strings were stored also I can
On Jun 16, 2011 7:06 AM, "GregM" gregorym@gmail.com wrote:Is the data store compatible between the two versions?
On Jun 16, 12:06 am, Yaw Anokwa yano...@gmail.com wrote:
you should try the beta instead of the alpha. it should be more
stable. that said, we can't guarantee that the betas and alphas are
rock solid, so you should test yourself before using it in an actual
deployment.On Thu, Jun 16, 2011 at 04:01, GregM grego...@gmail.com wrote:
ODK:
Hi,
I am about to deploy Aggregate v1.0 ALPHA SIX. I'd like to know:
- How stable is it?
Do you know of any serious problems in that version? Particularly
ones
that would corrupt data or cause data loss?Thanks!
Greg--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options:http://groups.google.com/group/opendatakit?hl=en--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com