On Sep 28, 2011, at 10:08 AM, Kirk Strauser wrote:
I get what you're saying, truly, and agree with the underlying argument: SQLA
is an ORM, not a data validator, template parser, or cheese grater. But I
would contend that the kind of validations I'm proposing would operate on the
level
On Sep 28, 2011, at 9:45 AM, Michael Bayer wrote:
Also, there are type-based validations, fine, string, numeric, integer,
dates, including length of strings. If someone throws on postgresql.INET,
not really, unless the contract of TypeEngine objects is extended such that
they *all* get
Does SA natively support (or is there a module on PyPI that supports)
client-side validation of SQLAlchemy objects? For example, I have this
declarative class:
class ImportedPayment(Base):
__tablename__ = 'importedpayment'
__table_args = {'schema': 'public'}
On Sep 27, 2011, at 1:57 PM, Kirk Strauser wrote:
Does SA natively support (or is there a module on PyPI that supports)
client-side validation of SQLAlchemy objects? For example, I have this
declarative class:
class ImportedPayment(Base):
__tablename__ = 'importedpayment'
