Query contains no columns when it has no records

[andybellenie]

Getting an empty query (no columns) when both a) using pagination (page=1) and the query returns no rows.

[rip747]

was this working before or is it something that i messed up when trying to get the oracle support working?

would you be able to write a test for this? I can then do a bisect and see which commit is the culprit that is causing the regression.

[rip747]

what database was this on?

[andybellenie]

SQL Server.

I've added a test for it here: andybellenie@76710fb

[rip747]

You are the man!
On Dec 13, 2012 8:47 AM, "Andy Bellenie" notifications@github.com wrote:

SQL Server.

I've added a test for it here: andybellenie@76710fbhttps://github.com/andybellenie/cfwheels/commit/76710fba179d2508c0150ac94b66b2cdd78db89c

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-11334824.

[rip747]

looking into this, I don't see this as a bug. When performing a paginated search, the first query passed to the database is just a count seeing if there are any records. If there are no records, then there is no reason to perform the extra work to perform the second query which actually queries the database for the records.

[andybellenie]

The second query contains the column list, which is often used to drive functionality. It also means that the result of the query depends on whether or not you enable pagination.

[rip747]

to me this seems like a non-issue and logic in the findall method is a complete mess. But if you're willing to give it a shot, you have my blessing :)

[andybellenie]

I thought you'd say that :)

[rip747]

hehehe... yes I am evil 😈, but you know I'll be doing some research on this as well. I'll update the ticket with my findings.

[perdjurner]

Correct me if I am wrong but this was not an issue on 1.1.8, right?

Closing.