DBI Fetches don't work

ido50 has asked for the wisdom of the Perl Monks concerning the following question:

In continuation with my previous node, I have found out that, as oppose to my previous suspicion, it's not the SQL INSERT statements that don't work on my database (SQLite on a FreeBSD server), but actually the DBI fetch routines. Using any of the following subroutines: fetchrow_array, fetchrow_arrayref, fetchrow_hashref, dump_results after executing a SELECT statement causes the program to exit silently, giving no error messages from RaiseError. Checking DBI->err after a fetch statement is impossible since the program exits before getting to the check.

Anyone knows why this might happen?
Thanks,
Ido.

-------------------------
Live fat, die young

Comment on DBI Fetches don't work Select or Download Code

Replies are listed 'Best First'.
Re: DBI Fetches don't work by mpeppler (Vicar) on Nov 12, 2004 at 13:49 UTC
There was a thread a few days ago about a problem with DBD::SQLite where it would SEGV on certain calls to prepare and/or fetchrow. See New way to segfault: selectrow_array() with placeholders, DBD::SQLite for some details. Michael	[reply]
Re^2: DBI Fetches don't work by ido50 (Scribe) on Nov 12, 2004 at 15:10 UTC
Well I've read it, but it doesn't really match my problem. That node talks about using `select` routines with a pre-prepared statement handle. My `$sth` is fresh... ------------------------- Live fat, die young	[reply] [d/l] [select]
Re^3: DBI Fetches don't work by mpeppler (Vicar) on Nov 12, 2004 at 15:26 UTC
Turn on DBI tracing (DBI->trace(4) or higher) to see what may be going on. Check to see if your program is dying due a signal of some sort (SEGV, or other) - enable core dumps (ulimit -c unlimited) to try to get a core that you can use to get a stack trace (if a core is generated). Michael	[reply]
Re^4: DBI Fetches don't work by ido50 (Scribe) on Nov 12, 2004 at 16:27 UTC
Re: DBI Fetches don't work by steves (Curate) on Nov 12, 2004 at 13:45 UTC
Have you tried putting the exiting call in an eval block to catch the error? Something like: `eval { $sth->fetch(); }; print "fetch error: $@\n";` [download]	[reply] [d/l]
Re^2: DBI Fetches don't work by ido50 (Scribe) on Nov 12, 2004 at 14:23 UTC
Tried, no luck... ------------------------- Live fat, die young	[reply]
Re^3: DBI Fetches don't work by steves (Curate) on Nov 12, 2004 at 14:26 UTC
Yeah, after I posted that I was thinking, if you see no error you're not going to catch one via eval ... My next step would usually be to go to the source and try to add some debug and/or try to get in touch with some people intimate with the code.	[reply]


"be consistent"
	PerlMonks