the password was hashed. i think to query name and password together may take less db ops if password is wrong. isn't it?
On 9月5日, 下午1时43分, Nick Johnson <[email protected]> wrote: > Also, you don't need to index the password field - just fetch the user, then > check the password. I sincerely hope you're not storing the password in the > clear, though! > > -Nick > > > > > > > > > > On Mon, Sep 5, 2011 at 3:02 PM, Simon Knott <[email protected]> wrote: > > Hi, > > > You need to retrieve all objects that were written in this period out of > > the datastore and re-put them - single-property indexes are only written on > > putting the entity. If you can't work out which entities were written in > > this period, then you will need to retrieve all entities and re-put them. > > > It should be noted that query indexes, which use these single-property > > indexes in the background, are re-generated on deployment. > > > Cheers, > > Simon > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To view this discussion on the web visit > >https://groups.google.com/d/msg/google-appengine/-/VYJDjjca21MJ. > > > 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. > > -- > Nick Johnson, Developer Programs Engineer, App Engine -- 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.
