From: Chris Hardie <chris@summersault.com>
To: pgsql-interfaces@postgresql.org
Subject: DBI w/Postgres
Date: Thu, 3 Sep 1998 16:52:23 -0500 (EST)
Message-ID: <Pine.NEB.4.02.9809031635280.727-100000@summersault.com> (raw)
The setting: Postgres95, Perl 5.004, latest DBI with latest Postgres
driver
The problem: I'm going along fine inside my Perl script that is selecting
and updating a database, until we get to the updating part (I can select
just fine). With DBI_TRACE = 2, I see:
----------
dbd_st_execute
dbd_st_execute: statement = >update test set value_2 = 3<
PQcmdTuples (UPDATE) -- short input from serverSegmentation fault (core dumped)
----------
Gasp! The SQL statement works fine inside of psql, and it seems
reasonable that Postgres would only return a curt "UPDATE" as it does in
psql. I don't understand why DBI doesn't like this. Do you?
Thanks,
Chris
---------------------------------------------
Chris Hardie chris@summersault.com
http://www.summersault.com/chris
magna vis veritatis
---------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: chris@summersault.com
Subject: Re: DBI w/Postgres
In-Reply-To: <Pine.NEB.4.02.9809031635280.727-100000@summersault.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox