Re: Concurrent testing PostgreSQL Vs MySQL - Mailing list pgsql-general

From Durai
Subject Re: Concurrent testing PostgreSQL Vs MySQL
Date
Msg-id 0f9001c3b028$33d9fb90$1a0110ac@dumco
Whole thread Raw
In response to Concurrent testing PostgreSQL Vs MySQL  ("Durai" <visolve_postgres@lycos.co.uk>)
Responses Re: Concurrent testing PostgreSQL Vs MySQL  (Shridhar Daithankar <shridhar_daithankar@myrealbox.com>)
Re: Concurrent testing PostgreSQL Vs MySQL  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-general
Hello Sridhar,

                    Now, It works. Thanks lot.

But Still I have doubt:

1. How MySQL works in this case? It has any default "autocommit"?

2. Is there any other method to test for "concurrent testing"?

Regs,
Durai.
----- Original Message -----
From: "Shridhar Daithankar" <shridhar_daithankar@myrealbox.com>
To: "Shridhar Daithankar" <shridhar_daithankar@myrealbox.com>
Cc: "Durai" <visolve_postgres@lycos.co.uk>; <pgsql-general@postgresql.org>
Sent: Friday, November 21, 2003 5:28 PM
Subject: Re: [GENERAL] Concurrent testing PostgreSQL Vs MySQL


> Damn.. I forgot to begin the transaction..
>
> Shridhar Daithankar wrote:
> > Durai wrote:
> >> Hello Shridhar,
> >>                     The script content is:
> >> ** *# cat te**stpgsql.php*
> >> *
> >> *<?php
> >> $dbconn = pg_connect("host=172.16.1.158 port=5432 dbname=test
> >> user=postgres");
>
> $result = pg_exec ($dbconn, "begin;");
>
> >> $result = pg_exec ($dbconn, "update table2 set C2=C2+1;");
> >> $result = pg_exec ($dbconn, "update table2 set C2=C2-1;");
> > $result = pg_exec ($dbconn, "commit;");
> >> pg_close($dbconn);
> >> ?>
> >> #
>
> Check this..
>
>   Shridhar
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 11/11/2003

pgsql-general by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: tsearch2 column update produces "word too long" error
Next
From: "Jason Tesser"
Date:
Subject: linking postgre to AD