-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Randall Nortman
Sent: 22 September 2009 16:31
To: sqlalchemy
Subject: [sqlalchemy] Pre-commit validation spanning multiple
tables/ORM classes
[SNIP]
So if I do this with
My issue with SQLA validators is that they don't allow inconsistent
state even on fields of a single object, which makes multi-field
validation impossible.
Eg. imagine you have fields tax_id and country_code on a customer
object. For country code 'us', tax_id should be 9 digits long; for
country
bojanb wrote:
My issue with SQLA validators is that they don't allow inconsistent
state even on fields of a single object, which makes multi-field
validation impossible.
meaning, you set A.a and you can't depend on A.b being correct yet ?
Well sure. How would you have it done ? Something
meaning, you set A.a and you can't depend on A.b being correct yet ?
Well sure. How would you have it done ? Something has to trigger the
validate event at some point. So if you need to wait for all of A.a,
A.b, A.c, etc. to be setup first, then sure you'd throw your validation
into
