24 Mar
2003
24 Mar
'03
1:07 p.m.
On Mon, Mar 24, 2003 at 05:57:01PM +0100, Beck, Mike wrote:
so you are doing:
BEGIN
UPDATE ...
UPDATE ...
UPDATE ...
SELECT (and check results)
COMMIT
you are expecting the SELECT to show the effect of UPDATE yes? It
shouldn't show any changes to the tables until you do COMMIT.
What we DO need to accomplish the above, is something to check that the
queries are 100% valid, without running them.
One other possible solution to this, abusing persistant connections:
Is it possible to serialize the connection info in some way, and
preserve it in a table maybe? That way it should be portable between
Apache instances, or is that asking too much?
The only
workaround that is possible if we want transaction support in
PMA would be to buffer the queries inside PMA, using our own seperate
table, and then sending them atomically to MySQL on COMMIT or just
dumping them on ROLLBACK.
no, i don't think that'd stand a chance - if i
have a big table and want to
do a updatequery on it and afterwards check if everything looks fine before
doing commit or rollback, that'd mean PMA would do a copy of my big table on
the heap for as long as it takes me to decide wether i like it? i doubt that
any ISP would like that behaviour. but it is kind of sad, to see that here we seem to
come to a point where
MySQL is offering a useful feature that users will not be able to use with
PMA - for usage of transactions i now installed the MySQL Controlcenter here
again ;-(
This is only because the transactionless nature of HTTP is conflicting.
--
Robin Hugh Johnson
E-Mail : robbat2(a)orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85