On Fri, 25 Feb 2000, Karl DeBisschop wrote:
>
> > From: <[EMAIL PROTECTED]>
> > On Fri, 25 Feb 2000, Karl DeBisschop wrote:
> >
> > >
> > > >>To summarize, I stated that the following does not work with
> > > >>postgresql:
> > > >>
> > > >>> $dbh->{AutoCommit} = 0;
> > > >>> $
> From: "Keith G. Murphy" <[EMAIL PROTECTED]>
>
> Karl DeBisschop wrote:
> >
> > To summarize, I stated that the following does not work with
> > postgresql:
> >
> > > $dbh->{AutoCommit} = 0;
> > > $dbh->do("CREATE TABLE tmp (a int unique,b int)");
> > > while (<>){
> > >
> From: <[EMAIL PROTECTED]>
> On Fri, 25 Feb 2000, Karl DeBisschop wrote:
>
> >
> > >>To summarize, I stated that the following does not work with
> > >>postgresql:
> > >>
> > >>> $dbh->{AutoCommit} = 0;
> > >>> $dbh->do("CREATE TABLE tmp (a int unique,b int)");
> > >>>
Karl DeBisschop wrote:
>
> To summarize, I stated that the following does not work with
> postgresql:
>
> > $dbh->{AutoCommit} = 0;
> > $dbh->do("CREATE TABLE tmp (a int unique,b int)");
> > while (<>){
> > if (/([0-9]+) ([0-9]+)/) {
> > $rtv = $dbh->do("INSERT INTO tmp VALUES ($1,$2
On Fri, 25 Feb 2000, Karl DeBisschop wrote:
>
> >>To summarize, I stated that the following does not work with
> >>postgresql:
> >>
> >>> $dbh->{AutoCommit} = 0;
> >>> $dbh->do("CREATE TABLE tmp (a int unique,b int)");
> >>> $rtv = $dbh->do("INSERT INTO tmp VALUES ($1,$2)");
> >>>
>>To summarize, I stated that the following does not work with
>>postgresql:
>>
>>> $dbh->{AutoCommit} = 0;
>>> $dbh->do("CREATE TABLE tmp (a int unique,b int)");
>>> $rtv = $dbh->do("INSERT INTO tmp VALUES ($1,$2)");
>>> if ($rtv) {$dbh->do("UPDATE tmp SET b=$2 where a=$1")};
>>>
At 02:16 PM 24-02-2000 -0500, Karl DeBisschop wrote:
>
>To summarize, I stated that the following does not work with
>postgresql:
>
>> $dbh->{AutoCommit} = 0;
>> $dbh->do("CREATE TABLE tmp (a int unique,b int)");
>> $rtv = $dbh->do("INSERT INTO tmp VALUES ($1,$2)");
>> if ($rtv) {$
Don Baccus wrote:
> At 11:32 AM 2/22/00 -0500, Tom Lane wrote:
>
> >I see no way that allowing the transaction to commit after an overflow
> >can be called consistent with the spec.
>
> You are absolutely right. The whole point is that either a) everything
> commits or b) nothing commits.
>
> Ha
Sorry for my english, Tom, but the point is another, I'm talking about
transactions not about error messages.
This is only a stupid example how to abort a transaction, PostgreSQL aborts
automatically transactions if
an error occurs, even an warning or a syntax error.
I can believe that all other
Dmitry Samersoff wrote:
> On 22-Feb-2000 Jose Soares wrote:
> > begin transaction;
> > create table tmp(a int);
> > insert into tmp values (1);
> > insert into tmp values (10);
> > ERROR: pg_atoi: error reading "10":
> > Numerical
Jose Soares <[EMAIL PROTECTED]> writes:
> ---
> Interbase, Oracle,Informix,Solid,Ms-Access,DB2:
> ---
> connect hygea.gdb;
> create table temp(a int);
> insert into temp values (1);
> insert in
On 22-Feb-2000 Jose Soares wrote:
> begin transaction;
> create table tmp(a int);
> insert into tmp values (1);
> insert into tmp values (10);
> ERROR: pg_atoi: error reading "10":
> Numerical result out of range
> commit;
> select
12 matches
Mail list logo
