> > I think you mean (not date-range) and (not qualifier)? Otherwise you'll > have (true OR ...) if the params are present... But that's a very neat > trick! >
Ah, yes, that's of course what I meant. Was wasting mental cycles on parameter ordering... Use named parameters people! > I ran it past our DBA and he verified that the execution plan definitely > short-circuits the booleans with true / false (which was my initial concern > after being somewhat gunshy of 'OR' in queries due to performance problems > that has caused in complex queries). > You should also verify the `date < LEAST(NULL, MAX(date))` approach too. I suspect that the query planner will summarily eliminate the aggregate. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
