On Thursday, May 10, 2018 at 4:36:35 PM UTC-7, [email protected] wrote: > > Yeah, you have right, I was going around the "ANY" function even though > usage is much simpler. > But anyway it was doesn't resolve an issue with ESCAPE '\\' >
I think you are running into problems because PostgreSQL LIKE operator is documented to use the following syntax: expr LIKE pattern [ ESCAPE escape_char ] See https://www.postgresql.org/docs/current/static/functions-matching.html#FUNCTIONS-LIKE However, when combining with ANY/SOME, it appears to not accept the ESCAPE syntax. That may be considered a bug in PostgreSQL, you may want to ask the PostgreSQL if that is something that should be supported. In terms of not generating the ESCAPE syntax, it's currently used unconditionally by the generic SQL support to get consistent escape character support across databases so that Dataset#escape_like functions correctly. I don't think the syntax is required on PostgreSQL, where the escape character defaults to the backslash. I'll try to make a change to Sequel in the next version that does not use the syntax on PostgreSQL, assuming that doesn't cause compatibility issues. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
