Summary | Share is null check |
Queue | Horde Framework Packages |
Queue Version | HEAD |
Type | Enhancement |
State | No Feedback |
Priority | 1. Low |
Owners | duck (at) obala (dot) net |
Requester | duck (at) obala (dot) net |
Created | 10/23/2008 (6079 days ago) |
Due | |
Updated | 04/22/2014 (4072 days ago) |
Assigned | 11/06/2008 (6065 days ago) |
Resolved | 10/01/2009 (5736 days ago) |
Milestone | |
Patch | Yes |
State ⇒ Assigned
Taken from Michael Rubinsky
Assigned to Duck
check something else to see which query to run. Also, even if that
flag is set, won't that just modify the result of the select, and not
the actual comparison on the server itself?
Additional, even checking only for null values, we do an full table
scan, as NULL are actually not a value and the db will not use index.
State ⇒ Feedback
flag. This is intentional, I don't remember the details at the moment,
but setting it caused all types of problems with existing queries
elsewhere...hence the check for both '' and NULL.
State ⇒ Assigned
Priority ⇒ 1. Low
State ⇒ New
New Attachment: null.diff
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Share is null check
Type ⇒ Enhancement
modified to check both empty strings and null values for portability
reasons. But we can check DB connection options to see, if we convert
empty strings to null values or not. The patch looks the
MDB2_PORTABILITY_EMPTY_TO_NULL options and adds the correct comparation.