Richard Huxton wrote:
> I'm no guru myself...
Don't underestimate yourself, after all you found the code where it goes wrong
> Looks OK to me, except you'll not get any error message on the last row
> - the insert will be called after the fetch.
I do get an error message on the last row (assumin
On Wed, Jun 06, 2007 at 04:44:03PM +0100, Richard Huxton wrote:
> I've had a quick look at my copy of DBI.pm (Debian Etch - lives in
> /usr/lib/perl5/DBI.pm)
>
> Around line 1930, we have the error-handling for execute_for_fetch()
>
> else {
> $err_count++;
> my $err = $sth->err;
> push @$
Bart Degryse wrote:
I tend to exclude reason 1: I've dumped the whole array using a debugger and it
really contains what I return when looping through it.
As far as I can see it's rather reason 2: execute_for_fetch seems to fill the
array incorrectly, that is: it's a valid array, but the last v
I tend to exclude reason 1: I've dumped the whole array using a debugger and it
really contains what I return when looping through it.
As far as I can see it's rather reason 2: execute_for_fetch seems to fill the
array incorrectly, that is: it's a valid array, but the last value added to it
also
Bart Degryse wrote:
Using DBI->err was a leftover from earlier testing. $dbh_pg->err is of course
better. But it doesn't solve the problem.
I'm not sure what you mean with your second remark.
The call to my function ( SELECT dbi_insert3(); ) is one transaction I suppose.
According to the docu
Using DBI->err was a leftover from earlier testing. $dbh_pg->err is of course
better. But it doesn't solve the problem.
I'm not sure what you mean with your second remark.
The call to my function ( SELECT dbi_insert3(); ) is one transaction I suppose.
According to the documentation on execute_fo
Bart Degryse wrote:
I'm writing a function that fetches data in an Oracle database and stores it in
postgresql database.
The fetching from Oracle and the inserting in PostgreSQL both work correctly. I know this because with an empty target table and without an insert trigger the source data ge
I'm writing a function that fetches data in an Oracle database and stores it in
postgresql database.
The fetching from Oracle and the inserting in PostgreSQL both work correctly. I
know this because with an empty target table and without an insert trigger the
source data gets 'copied' perfectl
