Hi,
I've never hacked on pgAdmin yet, so I'm curious from those who have: What sounds like the smartest way to make updates in the Edit Grid not fail when connected to a database with default_transaction_read_only set to on? : 1. Just send every update wrapped in START TRANSACTION READ WRITE ... COMMIT ? 2. Don't do that by default, but trap the "error: transaction is read only" and reissue the update with START TRANSACTION READ WRITE in that case? 3. Query the backend for SHOW DEFAULT_TRANSACTION_READ_ONLY and then issue updates wrapped in START TRANSACTION READ WRITE only if it was ON? 4. Just send a SET SESSION DEFAULT_TRANSACTION_READ_ONLY TO OFF and forget about it? I'm asking because we noticed in 1.14.2 that it doesn't do any of these things yet, but just surprises the innocent user with the "error: transaction is read only". Thanks, Chapman Flack Dept. of Mathematics, Purdue -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
