[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dbi-dev
Subject:    DBD::MSQL 0.65pl8 aborts on INSERT, CREATE statements.
From:       Simon Rakov <Simon_Rakov () iongate ! staff ! ichange ! com>
Date:       1996-02-20 11:27:42
[Download RAW message or body]

Hi,

The problem documented below *also happens now*  with the original test script, 
* test2.pl * !!!  I get the same error about a statement handle, a hash, and a 
DESTROY ignored.  Seems like it only happens with CREATE and INSERT 
statements.  Any thoughts?

Thanks.

Simon Rakov

------------------------------------------------Original message 
follows-------------------------------------------------


Every time I run my little discussion script, which is written in procedural 
perl (not object-oriented) I get this error, and frequently, a core dump:

Statement handle DBI::st=HASH(0xa07c8) DESTROY ignored - never set up at 
discuss.t line 320.
Database handle destroyed without explicit disconnect at discuss.t line 320.

My script is called "discuss.t," and line 320 reads:

$sth = $dbh->prepare( $query );

where $query is a scalar containing a valid SQL query.  I copied this notation 
from the test2.pl script which came with my DBD distribution (DBD 0.60pl8, DBI 
0.65, perl 5.001m, Solaris 2.4).  You have doubtless concluded by now that I 
don't know what I am doing, and you'd be right.  I just used the stuff in 
test2.pl as a cookbook, expecting that if I copied the statements for 
connecting to a database, preparing a query, executing the query, fetching or 
inserting a row, and disconnecting from the database, I would be all right.  
Well, that assumption seems to be wrong.

Does anyone have any DOCUMENTATION for the DBI/DBD stuff?  I'd really 
appreciate an answer to questions like "what is a statement handle?  what does 
preparing a query mean?"  Is there an FAQ out there?

The funniest part of all this is that until a day or so ago, *the script worked 
properly* with exactly the same code to invoke the DBD. Any thoughts on what 
I've done wrong would be appreciated.

Yours sincerely,
Simon Rakov
AT&T New Media Services

[prev in list] [next in list] [prev in thread] [next in thread]