https://bugs.freedesktop.org/show_bug.cgi?id=55703
Lionel Elie Mamane <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ProposedEasyHack --- Comment #7 from Lionel Elie Mamane <[email protected]> --- (In reply to comment #5) > The query design view is there to help people who don't know SQL, (...) > The difference between = NULL and IS NULL is a bit subtle for a lot of > people. On the other hand, if we hide the difference from them, they will be baffled why comparison to a constant NULL works one way (NULL->true), but comparison to another field (that possibly contains NULL) works another way (NULL->false). Maybe a good solution would be to fill in the "IS" in the UI. That is when the user enters just "NULL", don't let just "EMPTY" standing in the condition line and do "IS NULL" behind the scene, but replace the user's NULL by "IS EMPTY" instead of replacing it by only "EMPTY". Maybe for extra clarity we could also always fill in the implicit "="? Not sure what would be the most user-friendly. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
