I don't think this is OT. I have had a similar error in which SELECT statements return fine under mod_cgi, but mysteriously get an extra null field underl mod_perl with Apache::DBI... I don't know what causes it, nor have I looked into it, but I think it is somewhat related to or caused by mod_perl or some of its' modules...
Issac PGP Key 0xE0FA561B - Fingerprint: 7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B ----- Original Message ----- From: "Joshua Chamas" <[EMAIL PROTECTED]> To: "Viljo Marrandi" <[EMAIL PROTECTED]> Cc: "modperl list" <[EMAIL PROTECTED]> Sent: Tuesday, November 27, 2001 1:19 Subject: Re: array's first element is empty > Viljo Marrandi wrote: > > > > Hello, > > > > Not sure if this is mod_perl related, but i hope someone can help me > > anyway. When i do DBI queries from mod_perl handler and put all returned > > results in array then array's first element is empty, I wonder why? I > > don't like to shift off first element every time i return the result. > > Has anyone seen this before and what could cause this? > > > > This is off topic for mod_perl, and should as such either not be posted, > or posted with a [OT] in the beginning of the subject line. > > The DBI mailing lists would be of greater help, listed here at: > > http://www.isc.org/services/public/lists/dbi-lists.html > > To answer your question, a query like: > > select nothing,something from table > > would have a undef value returned from the nothing column > if the data in that column were NULL. You probably should > remove the nothing column from your query instead of shifting > the results. > > --Josh > _________________________________________________________________ > Joshua Chamas Chamas Enterprises Inc. > NodeWorks Founder Huntington Beach, CA USA > http://www.nodeworks.com 1-714-625-4051 >
