If you save the user it has a key, and you can get a unique string
from it like this:
unique_keystring = str(myUser.key())
If you just want a unique string to use as a key, you could do this:
import uid
unique_key = str(uuid.uuid4())
Many ways to do it. I use keystrings because with a keystring you
can do db.get(keystring) or even pass a list of key strings and its
fast. If you use some property you have to query.
-Mike
On Nov 3, 11:29 pm, yejun <[EMAIL PROTECTED]> wrote:
> Why not just let user choose a user name?
>
> On Nov 3, 10:35 pm, Ryan Lamansky <[EMAIL PROTECTED]> wrote:
>
> > Mahmoud: The problem is that won't recognize if the user changes their
> > email address; it'll create a new entity and the user will lose
> > everything.
>
> > yejun: I thought about that, but there's no way to automatically know
> > that a new email address was changed from some old one. User
> > interaction is required. This requires an additional security system
> > to be built to verify that the user did indeed have the old email
> > address originally. There's also a possibility that the user will
> > start creating new content before realizing there's a problem,
> > creating the hassle of trying to merge the accounts.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
