Exclusive Range produces incorrect SQL query
Reported by Dan Kubb (dkubb) | December 14th, 2008 @ 04:01 AM
When creating a query using an exclusive Range (one created with three dots: ...), the wrong query is generated. Currently it uses BETWEEN, which is fine for inclusive Ranges, but it should use "property >= start_range AND property < end_range" for exclusive Ranges.
Comments and changes to this ticket
-
Dan Kubb (dkubb) December 14th, 2008 @ 04:02 AM
- State changed from “unconfirmed” to “accepted”
Attached script demonstrating the problem.
-
-
Dan Kubb (dkubb) January 7th, 2009 @ 10:04 PM
- State changed from “accepted” to “resolved”
This is resolved in:
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
