Re: Determining if a DBI SELECT comes back empty

[Zed_Lopez]

I think I don't understand. If you need the results for further processing when there are results, where's the memory penalty? When there are no results, you have an empty array, which involves trivial memory, and you move on.

You could do SELECT COUNT(*)'s in advance, but that does incur a performance penalty over what you're already doing.