No but to implement a unique constraint, I find key_names are usually the easiest way. But you're right, the email can change so he might need to add a second kind used to track the uniqueness of that field.
On Wed, Feb 2, 2011 at 12:58, Jeff Schwartz <jefftschwa...@gmail.com> wrote: > Since email addresses can change it isn't a good idea to use them in an > entity's id. > > On Feb 2, 2011 12:41 PM, "dudu" <eduardopich...@gmail.com> wrote: >> No solution folks? Any idea? >> How do you configure your unique fields? >> >> How can I use the email property to be part of the "Key". >> If is generated by* IDENTITY strategy*, do I need to interfere? >> >> Could someone just post some working code with a Key, and some unique >> fields? >> >> -- >> 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. >> > > -- > 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. > -- 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.
