Well, the other day I ran into a fun little issue. I have code with transactions that is sending a "PREPARE TRANSACTION ..." followed by the "COMMIT TRANSACTION ..." to our master database, which is replicated using pgpool to a couple slaves.
Immediately after it sends the prepare transaction, the code errors out with this message from the server: NOTICE: Could not create inbox message because (sql_state=0A000) ERROR: cannot PREPARE a transaction that changes a table being replicated Query: PREPARE TRANSACTION 'bda3f9ed15249cc40003b560f7e902bec3a74c7c77cbe0055b129f6ccdcc9ed2' I was able to work around the problem using good ol' raw SQL begin, commit and rollback in my exception handling. But, I wasn't happy with that - it's so inelegant. I've been through the source and docs for transactions, and don't see a way to tell it to use simple begin/commit/rollback transactions. Is this not built in? Thanks, Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
