Try replace: db.PromoUnit.sequenceNumber.requires=IS_IN_SET(['1','2','3'],zero='select a value') db.PromoUnit.sequenceNumber.requires=IS_NOT_IN_DB(db(db.PromoUnit.sequenceNumber==request.vars.sequenceNumber),
with: db.PromoUnit.sequenceNumber.requires= (IS_IN_SET(['1','2','3'],zero='select a value'), IS_NOT_IN_DB(db(db.PromoUnit.sequenceNumber==request.vars.sequenceNumber)) db.PromoUnit.sequenceNumber.widget = SQLFORM.widgets.options.widget( db.PromoUnit.sequenceNumber, db.PromoUnit.sequenceNumber.default) On Monday, 2 July 2012 03:59:08 UTC-5, Annet wrote: > > In a table definition I have the following validators: > > db.PromoUnit.promoPositionID.requires=IS_IN_DB(db,'PromoPosition.id','%(name)s',orderby='PromoPosition.id',zero='select > > a value') > db.PromoUnit.sequenceNumber.requires=IS_IN_SET(['1','2','3'],zero='select > a value') > db.PromoUnit.sequenceNumber.requires=IS_NOT_IN_DB(db(db.PromoUnit.sequenceNumber==request.vars.sequenceNumber),db.PromoUnit.promoPositionID,error_message='combination > > promo position sequence number already in database') > > > The IS_NOT_IN_DB validator removes the IS_IN_SET drop box of > sequenceNumber, is there a way to prevent this from happening? > > > Annet >
