> Fabien COELHO <[EMAIL PROTECTED]> writes: > > Please find attached a patch which allows "LIKE/ILIKE/NOT LIKE/NOT ILIKE" > > as operators for ANY/SOME/ALL constructs. > > This seems to allow a whole lot of unintended and probably uncool things > as well. "ORDER BY NOT LIKE", for instance.
Yes. Well, it seemed to me (maybe I'm wrong here/) that "ORDER BY !~~" was allowed anyway by the parser, so I cannot see why it should not allow "NOT LIKE" as well, even if it does not make sense. I guess that it is filtered out later anyway? Or the rule factorization must be changed. It can also be done. -- Fabien Coelho - [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
