> a field should be marked alternativeid only if it should be unique. > not the other way ;-) .
Erm - no. The way it is it's the right way - if something is supposed to be working as uniquely identifying something, it must be a unique column. > valid policy may be to require the forgetter to enter username AND > email. this way, someone able to intercept the mail of an user should > provide minimal proof of identity. > > conversely, if we'd aggree to send a password to any email address > someone requests a remainder for, there would also be no problem to > send a list of username and password pairs. What's the usecase for someone to have several accounts - with one email? About 100% of all online applications I'm registered require me to provide a unique mail, or even use my mailaddress as login. So I consider this the sensible default in the TG identity model. But you can change that for your apps in about 20 secs. So - where is the reason for this discussion? Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
