Like I posted in my first response, the best way (I know of) to make a field unique is to use it as a key-name -- possibly on a *different* kind used for tracking uniqueness. Search the groups, there are probably already ready-to-use implementations.
I generally agree with Ikai's statement about "learning how to not overdo things." Make sure you think about why a field is being made unique, and the realistic frequency of changes to that field, when designing a solution to this problem. Not a lot of value spending weeks to design "the perfect" solution based on a non-fatal (to the app) highly unlikely scenario when a Good Enough solution (ie separate uniqueness marker entities) exists. My 2ยข. Robert On Fri, Feb 4, 2011 at 18:47, dudu <[email protected]> wrote: > Oh God...thanks folks, I used email just as example, I have other fields > with this constraint problem. > > -- > 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.
