Re^3: DBI don't fetch my data...or at least not all records (bug?)

[tye]

in reply to Re^2: DBI don't fetch my data...or at least not all records
in thread DBI don't fetch my data...or at least not all records

bad FILE descriptor? I don't use a file

It has to connect to the DB somehow. There is almost always a file descriptor under the covers (usually to a socket).

But it could also be reporting $! even though there wasn't a failure that set $! ("bad file descriptor" is a common error that gets left behind in $! due to common stuff that happens under the covers).

It looks like a bug to me.

[kurreburre]

Hi Thanks for answering. Do you mean a bug in DBI or in my program? I would say in DBI ( I might definiteley be wrong) because as I have stated before I do pretty the same select statment for some other columns and the only differece is that in the failing one the column "BBTicker" has the "not null" property set to it, the other "working" "BBTicker" columns in the other tables doesn't.

[tye]

Most likely a bug in DBD::ODBC, but that is just a guess. It could be a bug in ODBC or in your code or even in DBI, Perl, ODBC, etc.

Perhaps you should report exactly what data should get returned for the record where this fails, since that seems a likely place for this (possible) bug to have been triggered.