Re: [Dbi-interbase-devel] Coredump using Tie::DBI

[Edwin P. <ed....@co...>]

Michael Samanov wrote:
> 
> Never mind. Set $dbh->{RaiseError} = 0 and skip this message. It keeps
> silent  when  you  tie  from  DBD+auth,  but  when  you use the handle
> existent it cusses like this. Lincoln issues "LISTFIELDS" first (MySQL
> only?),  then,  should  it  fail, he tries "SELECT * FROM $table WHERE
> 0=1" and takes $sth->{NAME}. It doesn't harm though annoys.

After making some changes to Tie/DBI.pm, and run again your code sample,
I've got this silly error:

    -> prepare for DBD::InterBase::db (DBI::db=HASH(0x82046e8)~0x8204670
'insert into users (pass,login) values (?,?)')
 
......... then ..........

out_sqlda: sqld: 0, sqln: 1. done_desc: 1.
    <- prepare= DBI::st=HASH(0x821045c) at DBI.pm line 463.
    -> execute for DBD::InterBase::st (DBI::st=HASH(0x821045c)~0x8204928
'test' 'joe')
dbd_bind_ph

........ and we know that this will happen:

dbd_st_execute: calling isc_dsql_execute..
    ERROR EVENT -803 'Invalid insert or update value(s): object columns
are
constrained - no 2 table rows can have duplicate column values
-attempt to store duplicate value (visible to active transactions) in
unique index "USERS_I1"
' on DBI::st=HASH(0x8204928)
Invalid insert or update value(s): object columns are
constrained - no 2 table rows can have duplicate column values
-attempt to store duplicate value (visible to active transactions) in
unique index "USERS_I1"
 error -803 recorded: Invalid insert or update value(s): object columns
are
constrained - no 2 table rows can have duplicate column values
-attempt to store duplicate value (visible to active transactions) in
unique index "USERS_I1"

Tie::DBI attempted to do an INSERT, instead of the expected UPDATE.

Rgds,
Edwin.