Thanks Nick. Always appreciate the help!
Regarding the prefix you put in the key_name, on hunch it looks to
have other benefits. I suspect memcache. Do you have any other
pearls you can toss out about it, and ways that known key_name
prefixes can be leveraged?
--Daniel Rhoden
On Aug
(db.UserProperty) )
...
related resources:
http://code.google.com/appengine/docs/python/datastore/propertyclass.html
http://googleappengine.blogspot.com/2009/07/writing-custom-property-classes.html
--Daniel Rhoden
--~--~-~--~~~---~--~~
You received
What can I do about an app name I registered but doesn't appear in my
app list, nor can I register for it now because App Engine thinks it's
taken.
Who else would really want 'cleanslatesoaps'?
Thanks,
Daniel
--~--~-~--~~~---~--~~
You received this message
A String can go a long way as well. Hopefully your property table has
some sane restrictions as to what can go in it.
On Jul 29, 2009, at 3:00 AM, Tobias wrote:
You may want to use an expando as described here
http://code.google.com/appengine/docs/python/datastore/expandoclass.html
On
to 'http://mydomain.mydomain.com/'
So I'm wanting to know, is there a way I can have 'mydomain.com' BE my
domain for my app?
Thanks.
Also, will there be any DNS offerings?
--Daniel Rhoden
Guntersville, Alabama
--~--~-~--~~~---~--~~
You received this message
up as in use if a
gmail account exists with that username. If that's your gmail
account, you can sign in with it and use it to create the app.
-Nick Johnson
On Wed, Jul 29, 2009 at 3:46 AM, Daniel Rhoden drho...@gmail.com
wrote:
What can I do about an app name I registered but doesn't
activate your
gmail account so you can use it to create the app. Once you've done
so, you can add your other address as an administrator on the app,
so you don't have to manage two separate accounts.
-Nick Johnson
On Wed, Jul 29, 2009 at 5:31 PM, Daniel Rhoden drho...@gmail.com
wrote
I did the same thing and learned that you can't do decimal version
number, only integers. (oh the waisted time)
On Jul 29, 2009, at 11:53 AM, Joshua Smith wrote:
Figured it out. There was a syntax error in my .py file, and I was
getting this weird error, instead of the usual stack trace
