Needs work
Project:
Drupal core
Version:
main
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Apr 2011 at 22:00 UTC
Updated:
24 Jan 2025 at 12:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
damien tournoud commentedI can confirm this, and it is actually a bug. We need to fix it in D8, then backport.
The gist of the bug is:
We need to extend the tests.
Comment #2
daften commentedOk, perfect, now it's confirmed it's a bug, I'll try to create a patch.
Comment #3
daften commentedPatch put in attachment
Comment #4
daften commentedComment #5
daften commentedWhat needs to happen next, some body reviews it and then it gets updated to reviewed and tested by community?
Comment #6
daften commentedCan somebody review this?
Comment #7
scronide commented#3: pager-bug-1133880-2.patch queued for re-testing.
Comment #19
lendudeUnfortunately this comment is unclear about the purpose:
// A NULL limit is the "kill switch" for pager queries.Is it a kill switch for the query or a kill switch for the paging of the query?
As it stand now, this would be a behaviour change, and would need to be done in a BC fashion if we do want to change this. I would say this is "works as designed" now, but I'll ask in #bugsmash for other opinions.
Comment #20
lendudeDidn't mean to switch the component, force of habit....
Comment #24
johnvIMO the comment
// A NULL limit is the "kill switch" for pager queries.is a clarification for configured/headless views.When using the View UI, the UI should avoid having an empty value. Issues exist for that. Will link later.