On Mon, 2006-02-20 at 10:40 +0100, Thomas Mueller wrote: > Aaron Stone wrote: > > I managed to forget to add the replycache table to my database, so the > > query failed the first time. The second time, the query didn't just > > fail, it was ignored. This continues even for queries to tables that > > exist, until the end of the process. > > > [..] > > [ERROR: current transaction is aborted, commands ignored until end of > > transaction block > > ] > > Until the end of the transaction, that is until you do a 'rollback'. > > To ignore everything makes sense: why put load on the database if > everything will be undone later?
Of course -- the issue is that we're not handling the error elegantly, but rather just throwing the rest of the queries at the server and hoping that we've coded somewhat defensively against query errors. It's actually kinda just fine as it is. The errors are logged, and a temporary error code is returned, causing the message to remain queued by the SMTP server. Aaron
