Re: update phenomenom

ok, you are right.

I checked it once more, and now it worked....

thanks for your help,

--

Mit freundlichem Gruß

Henrik Steffen
Geschäftsführer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com          Tel. +49 4141 991230
mail: steffen@topconcepts.com       Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline:  +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
Ihr SMS-Gateway: JETZT NEU unter: http://sms.city-map.de
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------

----- Original Message -----
From: "Jan Wieck" <JanWieck@Yahoo.com>
To: "Henrik Steffen" <steffen@city-map.de>
Cc: "pgsql" <pgsql-general@postgresql.org>
Sent: Saturday, June 07, 2003 10:03 PM
Subject: Re: [GENERAL] update phenomenom


> Henrik Steffen wrote:
> > hi,
> >
> > I tried both:
> >
> >  $command="UPDATE table SET miano='12345'; commit; ' WHERE ... ;";
> >
> >
> > and
> >
> >  $command="UPDATE table SET miano='12345'; -- ' WHERE ... ;";
> >
> >
> > neither worked.
>
> What do you mean "neither worked"?
>
> the second form works just like a charm. I checked it with PG 7.3.3, DBI
> 1.14 and DBD::Pg 0.95.
>
> >
> > it just gives an error and dies.
> > no update done.
>
> What error and where is that coming from? If I use the comment hack it
> doesn't show any message in the postmaster log. It is totally happy with
> it and shows exactly the symptom you described.
>
> > I looked at man DBI, but couldn't find any restriction
> > for $dbh->prepare() .... I am not sure, if it's possible
> > to pass multiple statements to the prepare-method.
>
> I'm not too familiar with Perl, but if DBD blindly forwards the query
> given in the string argument of prepare() into libpq's pg_exec() ... and
> it is supposed to do it that way ... then it is possible to pass
> multiple statements. This is a long standing functionality of the
> frontend/backend protocol.
>
>
> Jan
>
> --
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #================================================== JanWieck@Yahoo.com #
>