http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8594
Priority: P5 - low
Change sponsored?: ---
Bug ID: 8594
Assignee: [email protected]
Summary: A report containing a subquery that has a 'limit' will
have that limit stripped out
Severity: normal
Classification: Unclassified
OS: All
Reporter: [email protected]
Hardware: All
Status: NEW
Version: rel_3_8
Component: Reports
Product: Koha
The limit is stripped out when Koha fetches the headers* so that another limit
can be applied. However, if you have a subquery in the fields part, then you
probably need to apply a limit for things to work. So fetching the headers
fails.
I'm thinking that the limit should be removed after the last where clause, or
if there's no where clause, do what is currently done. This won't fix every
case, but should result in more things working.
* in other news, I'm not a fan of it having to run the query twice, which it
seems to do, just to grab the headers.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
