Hi Ron,
Do you mean plug in the work undef before doing the INSERT?
Thanks.
Peter Loo
-Original Message-
From: Ron Savage [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 19, 2006 9:39 PM
To: List - DBI users
Subject: Re: Bad int8 external representation (SQL-HY000)(DBD:
st_execute
]; List - DBI users
Subject: Re: Bad int8 external representation (SQL-HY000)(DBD:
st_execute/SQLExecute err=-1)
It's a numeric field and you are trying to insert an empty string rather
than undef (equivalent to null).
When you queried the other database and had the values in memorynot
written
On Thu, 20 Apr 2006 07:51:24 -0700, Loo, Peter # PHX wrote:
Hi Peter
Do you mean plug in the work undef before doing the INSERT?
Yes. Off the top of my head (add error checks!):
$sql = 'insert into table_x (column_y, column_z) values (?, 99)';
$sth = $dbh - prepare($sql);
$sth -
.
Peter Loo
Wolters Kluwer Health
(602) 381-9553
-Original Message-
From: Ron Savage [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 20, 2006 4:14 PM
To: List - DBI users
Subject: RE: Bad int8 external representation (SQL-HY000)(DBD:
st_execute/SQLExecute err=-1)
On Thu, 20 Apr 2006 07:51:24
Ron Savage said:
On Thu, 20 Apr 2006 07:51:24 -0700, Loo, Peter # PHX wrote:
Hi Peter
Do you mean plug in the work undef before doing the INSERT?
Yes. Off the top of my head (add error checks!):
$sql = 'insert into table_x (column_y, column_z) values (?, 99)';
$sth = $dbh -
On Thu, 20 Apr 2006 16:33:14 -0700 (PDT), William R. Mussatto wrote:
Hi William
$sql = 'insert into table_x (column_y, column_z) values (?, 99)';
$sth = $dbh - prepare($sql); $sth - execute(undef); -- Cheers
Minior change: should it not be:
$sth - execute((undef));
Well, no. Firstly I
On Thu, 20 Apr 2006 16:21:29 -0700, Loo, Peter # PHX wrote:
Hi Peter
Yes, thanks. I have it working now. Now I am working on the
UPDATE from a SELECT. I am having problem with char columns. I am
working on a routine that will identify the columns that require
quotes and dynamically plug
No Ron. I did not chomp the record, but I am quite certain that it is
not the issue. The field it is complaining about is blank. The odd
thing is that the column it is going into is allowed for NULL values.
I don't know what else to do, but will certainly give chomp a try.
Yes, I am only
It's a numeric field and you are trying to insert an empty string rather
than undef (equivalent to null).
When you queried the other database and had the values in memorynot
written to a file... they stayed undef. When you split the row from the
file, you have empty strings rather than undef
On Wed, 19 Apr 2006 20:56:39 -0700 (PDT), Peter Loo wrote:
Hi Peter
No Ron. I did not chomp the record, but I am quite certain that it
is not the issue. The field it is complaining about is blank. The
odd thing is that the column it is going into is allowed for NULL
values. I don't know
On Tue, 18 Apr 2006 11:44:50 -0700, Loo, Peter # PHX wrote:
Hi Peter
[unixODBC]ERROR: copy: line 1, Bad int8 external representation
(SQL-HY000)(DBD: st_execute/SQLExecute err=-1)
Line 1, eh? First attempt to insert data? Did you try chomp-ing the line?
--
Cheers
Ron Savage, [EMAIL
11 matches
Mail list logo
