I tried the --default_partition="" flag but now validation.py is
throwing an exception:
Traceback (most recent call last):
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
google/appengine/tools/dev_appserver.py", line 4099, in _HandleRequest
default_partition)
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
google/appengine/api/validation.py", line 360, in __setattr__
value = self.GetValidator(key)(value, key)
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
google/appengine/api/validation.py", line 598, in __call__
return self.Validate(value, key)
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
google/appengine/api/validation.py", line 923, in Validate
'\'%s\'' % (value, key, self.re.pattern))
ValidationError: Value '""~tagassetspro' for application does not
match expression '^(?:[a-z\d\-]{1,100}\~)?(?:(?!\-)[a-z\d\-\.]
{1,100}:)?(?!-)[a-z\d\-]{1,100}$'
This has got to be a bug. It's not like using stored test data with
the dev server is some kind of oddball edge case ;-)
--Joe
On Jul 22, 4:57 pm, Chris Copeland <[email protected]> wrote:
> Thanks, Matthew.
>
> I was able to update to 1.5.2 and use my existing datastore by adding that
> flag.
>
> It would have been useful if the release notes had mentioned that this would
> be necessary.
>
> -Chrsi
>
> On Fri, Jul 22, 2011 at 2:39 PM, Matthew Blain
> <[email protected]>wrote:
>
>
>
> > That's a clever way to update the appid. I do not know if it works for
> > all cases (e.g. it may not work for all reference properties (stored
> > keys)) but is a neat trick.
>
> > Another way to deal with it is to use the --default_partition="" flag
> > rather than using an older version of the sdk.
>
> > --Matthew
>
> > On Jul 22, 12:17 pm, c h <[email protected]> wrote:
> > > hi all,
>
> > > i *think* that it is honoring your datastore location (though the log
> > > message is incorrect), but the change to rename your application to
> > > dev~<your appname> in development has just rendered all of our test data
> > > useless.
>
> > > after re-importing my test data it does look like it is stored where i
> > ask
> > > it to be, but under the new application name.
>
> > > if you are lucky enough to be using sqlite you can connect to the db and
> > > rename some tables to get it to work:
>
> > > sqlite3 local_appname_dev_sqlite.datastore
> > > sqlite> .tables
> > > Apps
> > > IdSeq
> > > Namespaces
> > > appname!!Entities
> > > appname!!EntitiesByProperty
> > > appname!namespace!Entities
> > > appname!namespace!EntitiesByProperty
> > > sqlite> alter table `appname!!Entities` rename to
> > `dev~appname!!Entities`;
> > > sqlite> alter table `appname!!EntitiesByProperty` rename to
> > > `dev~appname!!EntitiesByProperty`;
> > > sqlite> alter table `appname!namespace!Entities` rename to
> > > `dev~appname!namespace!Entities`;
> > > sqlite> alter table `appname!namespace!EntitiesByProperty` rename to
> > > `dev~appname!namespace!EntitiesByProperty`;
>
> > > where you substitute 'appname' for your application's name, and
> > 'namespace'
> > > for your datanamespace.
>
> > > cfh
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
