I don't think so. The validator in SQLObject trumps the FormEncode stuff. Instead of inherit from FancyValidator, it implements its own to_python/from_python(where the standard FormEncode way would be _to_python/_from_python, note the underscore). As a result, features(like if_missing etc.) listed in the FormEncode doc doesn't work in the SQLObject validator.
william wrote: > By looking deeper in the code, (if I'm correct), SQLObject use the > validator from formencode. > > My concern, is why must I put a validator in each of my save methods ? > This validators is the same ahs we have in SQLObject, no ? > > Why not having in the decorator a "default" behaviour where we will > transform automatically values as SQOobject woud like to see them ? > > You can grab the validator used in SQLObject by checking the > sqlmeta.columnList. > This list contains all the different table fileds and their > definitions. > > I think this is usefull because SQLObject is defacto part of TG. > > This can be very usefull when you have lot of Integer (or date) in your > forms. > > > > Thanks > > William
