Thanks Jason. I'm assuming if you use @Persistent on a User field it uses the email value to persist so the question then is what happens in the future if getUserId() is added?
Will the User object use that to persist? If so will that break tables that are persisting Users with the email address? -Aj On Aug 20, 12:06 pm, "Jason (Google)" <apija...@google.com> wrote: > Hi AJG. I imagine most people are using the User object or email address as > they did before the unique user ID was available in Python. It should be > coming for Java also. > - Jason > > On Wed, Aug 19, 2009 at 7:31 PM, AJG <ajgreg...@gmail.com> wrote: > > > From the docs it sounds like the User object is based on the email for > > the user. This seems really bad if you want to persist data for the > > current user since one day they can change their email address and > > then you are screwed. > > > I see the user_id() function for python and the fact that this doesn't > > exist for java seems like a huge mistake. > > > Are people just using User to persist anyway or is there another way > > around this? > > > Thanks in advance. > > -Aj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
