> SQLAlchemy sends to the log the statement and parameters it is to send > to the DBAPI cursor.execute() method, *before* it actually does so. > This so that if the DBAPI throws an exception, as is the case here, > one can see what instructions were sent to it which were the immediate > cause of this error.
Thanks for your explanation. Do I need to consider any more fine-tuning for my database session? > The mechanism of a UNIQUE constraint is that this is a database-level > construct, so the backend database is tasked with checking this > this condition and reporting on it at statement execution time. Should I get the exception "sqlalchemy.exc.IntegrityError" directly after I attempted to insert a second record set with unique attributes into a SQLite table? Regards, Markus -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
