Re: Disappearing results with DBI and bind

Just a couple of ideas, thinking out loud:

- I know this isn't related to your width/height issue, but is fetchrow() a valid DBI routine? I know that fetch() is an alias for fetchrow_arrayref(), but I've never seen plain old fetchrow() before.

- Are you sure the initial query runs ok? When something happens that I can't explain, I start by eliminating the immediately obvious things even though I know they can't possibly in a million years be wrong :-) Copying the query and pasting into a SQL shell gives a quick answer.

Chris
M-x auto-bs-mode

Comment on Re: Disappearing results with DBI and bind_columns Select or Download Code

Replies are listed 'Best First'.
(ar0n) Re (2): Disappearing results with DBI and bind_columns by ar0n (Priest) on Dec 31, 2001 at 04:30 UTC
- I know this isn't related to your width/height issue, but is fetchrow() a valid DBI routine? I know that fetch() is an alias for fetchrow_arrayref(), but I've never seen plain old fetchrow() before. Holy moly, you're right. I merely switched `fetchrow` to `fetch` and it worked. I find this highly odd, to tell you the truth. I've used DBI for a few years now, and started using `bind_columns` about 6 months ago, after a Perl Mongers meeting. Since then, I've always used `fetchrow`. I'm surprised it hasn't once given me an error message or even a warning. Thank you. [ ar0n -- want job (boston) ]	[reply]
Re: (ar0n) Re (2): Disappearing results with DBI and bind_columns by steves (Curate) on Dec 31, 2001 at 10:42 UTC
I'm not sure how you could have ever gotten bind columns to work with fetchrow. My understanding is that the fetchrow method is an old alias for fetchrow_array. I thought only plain old fetch returned values in bound columns since the others return their values in some sort of data structure -- an array in this case.	[reply]