Open GoogleCodeExporter opened 8 years ago
Yeah, this is a bad regression.
Original comment by bquin...@google.com
on 12 Mar 2013 at 10:37
Hi, could you post your app config? I'm trying to reproduce this, but no luck
so far.
Also, do you get the same error if you start the dev_appserver with
--auto_id_policy=sequential?
Thanks!
Original comment by roh...@google.com
on 12 Mar 2013 at 11:39
Also, are you loading a local datastore from a previous SDK version or from a
previous version of the same SDK?
If so, could you please try running with --clear_datastore (back up your old
data first) or with --datastore_path=<some other, possibly empty local
datastore>, and see if the error still occurs?
Thanks very much. Still looking into it, but currently cannot reproduce.
Original comment by roh...@google.com
on 13 Mar 2013 at 12:05
I launch the dev server with:
--require_indexes --log_level='debug' --datastore_path=...
So yes, I'm using a previous database.
Works fine if I point the --datastore_path parameter to something new/fresh.
Original comment by prat...@referabuyer.com
on 13 Mar 2013 at 12:21
I see. Unfortunately we don't guarantee backwards compatibility of local
datastores across SDK versions, although we do strive to maintain it.
I'm still not sure what's causing the issue in this case, as I've just run a
test using your demo code above, which succeeds in writing a 1.7.5 datastore,
then reading from it and writing to it in the 1.7.6 SDK. However, it's quite
possible the issue is triggered by some aspect of your configuration that I'm
missing.
If you're willing to share the datastore file in question I'll try again to
repro the issue. Otherwise, if it's possible to regenerate your local datastore
in the new SDK, I would recommend that for now.
I'll update this thread if or when we have a solution for migrating local
datastores across SDK versions.
Thanks!
Original comment by roh...@google.com
on 13 Mar 2013 at 5:02
[deleted comment]
Status update: a workaround for now is to set --auto_id_policy=sequential when
you start the dev appserver. That should allow you to write to your existing
dev datastore from 1.7.6.
There is no need to regenerate your data. This problem occurs when you try to
write to a SQLite dev datastore created with SDK version 1.7.4 or earlier from
the 1.7.6 SDK.
We are working on a fix for this. Thanks again for reporting it.
Original comment by roh...@google.com
on 13 Mar 2013 at 5:42
Original issue reported on code.google.com by
prat...@referabuyer.com
on 11 Mar 2013 at 10:02