in reply to DBI bug?

OK. Before suggesting that there is a DBI bug, did you go through the recommended routine checks?
The problem could be a syntax error in the SQL statement. Even if you say that you tested the statement in the database, what you tested was not the same, because it did not have embedded variables inside. So we shouldn't rule out the possibility of a quoting problem.

recommendations
  1. You could use the DBI->trace(2) method, to find out where exactly the flow of info between client and server is broken, and what query was passed.
  2. You could reduce your script to the minimum instructions that reproduce the error, (using strict and -w). If you can do it without quoting problems, i.e. by hardcoding the SQL string, then we could rule out some more things and start considering the possibility of a bug.
  3. Have a look at some tutorials that could help you to find out what could be wrong: Reading from a database, Tricks with DBI and The fine art of database programming.

Please give us some more info.
 _  _ _  _  
(_|| | |(_|><
 _|   

Replies are listed 'Best First'.
Re: Re: DBI bug?
by DaWolf (Curate) on May 06, 2002 at 12:32 UTC
    I've debugged the SQL statement by printing it to a text file and it is correct.

    I'm not trying to make DBI look bad, even because I think it's impossible, since it's one of the best nodes ever written, in my opinion.

    I'm just saying that there's a bug somewhere, maybe not in DBI, maybe in MS Access? All I know is that it should work and for some weird reason it doesn't...

    I'll try to clean the code to minimize the "noise" between the necessary code to run the query and the point it's generating the error, but I'm still pretty sure that is not a code error.

    my ($author_nickname, $author_email) = ("DaWolf","erabbott\@terra.com.br") if ($author_name eq "Er Galvão Abbott");