Update: (I'm going nuts) I downgraded to 1.5.1 (restored GoogleAppEngineLauncher.app) and still the same now ... It seems that the upgrade to 1.5.2 did some permanent damage. I am absolutely puzzled why --datastore_path= is ignored suddenly.
Here the full startup log: cat$ /Applications/GoogleAppEngineLauncher.app/Contents/Resources/ GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/ dev_appserver.py -d --datastore_path=/Users/cat/repositories/appengine/ my.datastore -p 8080 . INFO 2011-07-22 09:15:00,330 appengine_rpc.py:159] Server: appengine.google.com INFO 2011-07-22 09:15:21,578 rdbms_sqlite.py:58] Connecting to SQLite database '' with file '/var/folders/u5/u5xmrm5gHPGXhfjlyv98u+++ +TI/-Tmp-/dev_appserver.rdbms' INFO 2011-07-22 09:15:21,618 dev_appserver_multiprocess.py:637] Running application test on port 8080: http://localhost:8080 On 22 Jul., 09:22, Cat <katz...@gmail.com> wrote: > Hi, > > After today's upgrade my datastore is empty and my testdata is not > available. > > I start my SDK Server like this (usually with the MacOS Launcher): > dev_appserver.py --datastore_path=/Users/cat/repositories/appengine/ > my.datastore -p8080 . > > Strangely --datastore_path is ignored and the dev_appserver uses a new > datastore in the tmp directory: > INFO 2011-07-22 07:11:11,606 rdbms_sqlite.py:58] Connecting to > SQLite database '' with file '/var/folders/u5/u5xmrm5gHPGXhfjlyv98u+++ > +TI/-Tmp-/dev_appserver.rdbms' > > Can anyone tell me which flags to set to get my old test datastore > back? > > I would have to create lots of testdata manually that accumlated over > the last months. > > Regards, > Cat -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
