|
From: SourceForge.net <no...@so...> - 2010-08-06 19:58:27
|
Bugs item #3030096, was opened at 2010-07-15 17:39 Message generated for change (Settings changed) made by ioguix You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=418980&aid=3030096&group_id=37132 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Databases Group: None >Status: Closed >Resolution: Rejected Priority: 5 Private: No Submitted By: John Andrea (jandrea) Assigned to: Nobody/Anonymous (nobody) Summary: transaction support Initial Comment: It appears that transaction rollback works, but a commit seems to fail. Example against a small database given in attached file. Using phpPgAdmin 4.2.3 and Postgresql 8.4.4 on Linux. ---------------------------------------------------------------------- >Comment By: Guillaume `ioguix` de Rorthais (ioguix) Date: 2010-08-06 21:58 Message: Hey, This is not a bug. You have to realize phpPgAdmin is a web application. That means, each time you refresh a page, it opens a new database connection and close it at the end of the php script. Your transactions can obviously not survives in this environnement. If you want to use transaction, you will have to begin; ... ;commit; from the *same* page, so you will not be able to see the result, *then* commit them. Another solution would be to use *prepared* transaction, as described here: http://www.postgresql.org/docs/current/static/sql-prepare-transaction.html I leave this ticket open if you want to comment further. Cheers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=418980&aid=3030096&group_id=37132 |