[web2py] Re: IS_NOT_IN_DB backward incompatible change?

2010-09-23 Thread Jeremy Dillworth
There's just one more issue I wanted to raise. It didn't hit me until I was describing the situation to a non-technical friend. When the value is blank, the error message doesn't say the value is blank, it says value already in database. I wasted some time wondering where this mysterious blank was

[web2py] Re: IS_NOT_IN_DB backward incompatible change?

2010-09-23 Thread mdipierro
It is. fixing it. On Sep 23, 12:07 am, Jeremy Dillworth jdillwo...@gmail.com wrote: There's just one more issue I wanted to raise. It didn't hit me until I was describing the situation to a non-technical friend. When the value is blank, the error message doesn't say the value is blank, it

[web2py] Re: IS_NOT_IN_DB backward incompatible change?

2010-09-22 Thread mdipierro
Because it was undocumented I was allowed to change it. I changed it because I think the previous behavour was a bug. Allowing IS_NOT_IN_DB to validate as '' is like saying that '' is allowed in the referenced database field and (while technically possible) it is not a good idea to allow that.