> On Wednesday 28 April 2010, Ferdinand Gassauer wrote: > > https://blueprints.launchpad.net/openobject-server/+spec/constraints- extens > > ion > > > > any comments on this ? > > > > That's interesting. I would only cross-check that this mechanism will not add > any significant overhead. > > On another note, it may just be that Postgres constraints can also be seen > through a table/view, so that this module can access them. If done so (with > some postgres magic), we could expose those fast constraints to the UI and > thus configuration. > > On a sidenote, shouldn't constraint failures result in a custom Exception, > like 'osv_constraint_fail', so that we can handle them better at higher level? > > Hello Panos! Just wonder if you had time to think/check this idea
we are quite happy with this solution and given the many company specific constraints - which are necessary to avoid the many stupid mistakes happening every day which then have to be corrected manually - we would consider such soft constraint system very very usefully -- regards Ferdinand Gassauer ChriCar Beteiligungs- und Beratungs- GmbH Official OpenERP Partner _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
