[web2py] Re: IS_NOT_IN_DB on three fields

2012-08-08 Thread Annet
Hi Anthony, Did you move that validator from the promoPositionID field to the nodeID > field? No, I had it on promoPositionID and then reallized I had to include nodeID in the validation as well. I changed the validator but forgot to make it belong to the nodeID field. Now that I've corrected

[web2py] Re: IS_NOT_IN_DB on three fields

2012-08-07 Thread Anthony
Did you move that validator from the promoPositionID field to the nodeID field? The second version of the validator is checking for unique values in the nodeID field, not the promoPositionID field, so the validator belongs on the nodeID field. If you want it on the promoPositionID field, then it

[web2py] Re: IS_NOT_IN_DB on three fields

2012-08-07 Thread Annet
Hi Anthony, Looks like it should work. What do you mean it doesn't work? What are you > expecting, and what is happening instead? In case I enter the following records: nodeID promoPositionID sequenceNumber 2831 1 2831

[web2py] Re: IS_NOT_IN_DB on three fields

2012-08-07 Thread Anthony
Looks like it should work. What do you mean it doesn't work? What are you expecting, and what is happening instead? Anthony On Tuesday, August 7, 2012 3:13:36 AM UTC-4, Annet wrote: > > I have the following validator: > > IS_NOT_IN_DB(db(db.PromoUnit.sequenceNumber==request.vars.sequenceNumber),