a DBAPI error? we have no control over those. if it's an error that SQLA detects directly then it should be showing you all it knows.
On May 19, 2014, at 4:42 PM, Jonathan Vanasco <[email protected]> wrote: > occasionally, i run into this problem with Postgres; though it would likely > happen on other systems too. > > my database might miss a migration, and we end up with this situation > > SqlAlchemy Model - Column = varchar(1000) > PostgreSQL - Field = varchar(255) > Data = 500 characters in length > > When I try to insert data into the field, the error I get just shows me an > error on the table. It would be great if SqlAlchemy could identify which > column caused the error too. > > Similar issues happen when putting the wrong type of data into a field. > > I don't know if the DBAPI makes any of this data available, or even if the > database provides the driver with this sort of data. but if so, it would be > really useful. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
