> tested your patch and there was no change in result. I think it
> wouldn't be nice if this will point out a bug in the perl pg driver
> because I can't imagine that you would like to do such things in
> there ...
>
> the new crash-me tests results are sent to monty so I think he will
> put them online tomorrow (today for you I think). I also did a test
> run on oracle and on a microsoft sql 7 server on windows nt (oracle
> on linux).
Enclosed is a patch that shows our perl interface can't handle '--'
comments, even though psql and the backend directly can handle them.
To add complexity to this, the backend -d3 log from the perl test
session shows the same query that works perfectly in a direct backend
connection.
Can anyone suggest a cause for this?
---------------------------------------------------------------------------
StartTransactionCommand
query: CREATE TABLE person (id int4, name char(16)) --test
ERROR: parser: parse error at or near "--"
AbortCurrentTransaction
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
*** ./interfaces/perl5/test.pl.orig Thu Oct 7 20:25:13 1999
--- ./interfaces/perl5/test.pl Thu Oct 7 20:41:40 1999
***************
*** 147,153 ****
######################### create and insert into table
! $result = $conn->exec("CREATE TABLE person (id int4, name char(16))");
die $conn->errorMessage unless PGRES_COMMAND_OK eq $result->resultStatus;
my $cmd = $result->cmdStatus;
( "CREATE" eq $cmd )
--- 147,153 ----
######################### create and insert into table
! $result = $conn->exec("CREATE TABLE person (id int4, name char(16)) -- /* test*/");
die $conn->errorMessage unless PGRES_COMMAND_OK eq $result->resultStatus;
my $cmd = $result->cmdStatus;
( "CREATE" eq $cmd )