i do make use of the IS_NOT_IN_DB() validator. Note that you can still
have duplicates if 2 requests are received by GAE at nearly the same time.
assuming your requests are more than say 1 second apart, if IS_NOT_IN_DB()
is failing i would consider it a bug.
NOTE that GAE dev_appserver.py rele
Sorry to bump this up, but I have not been able of using unique as it is
described here (no validators).
Also I have tried to use instead of unique IS_NOT_IN_DB as in this other
thread is suggested:
https://groups.google.com/forum/?fromgroups=#!searchin/web2py/gae$20unique/web2py/ZepLjcBowZs/Fu
yes and no. It will not be enforced at the database level but if you
do not specify validators, it will use it to pick default validator
that enforce the uniqueness at the web2py level
On Sep 23, 11:17 am, Carl wrote:
> My db.py includes...
>
> db.define_table('voucher',
> Field('code', 'stri
3 matches
Mail list logo
