Why does the default auth.settings.table_user use IS_NOT_IN_DB for
enforce uniqueness on the email field instead of unique=True? I'm
curious because the example on creating your own auth table in the
book uses unique=True (which obviously enforces at the db level
instead of at the form level).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
