[jsr-221-eg] SQL 2016 MATCH RECOGNIZE JDBC parameter Marker / Escape Characters

Mark Rotteveel mark at lawinegevaar.nl
Tue Oct 9 18:17:22 UTC 2018


On 9-10-2018 20:07, Lance Andersen wrote:
>>
>> I see that that proposal contains some parts not explicitly mentioned 
>> in the current proposal (eg escaping \ within the escaped text, see 
>> below). Is that still the intent? Or did this change?
>>
>> --------------------
>> {\...\}
>>
>> expands to the characters between '{\' and '\}'. Doubled backslashes 
>> '\' expand to a single backslash.
>>
>> {\?\}  expands to ?
>> {\{fn sysdate()}\} expands to {fn sysdate()} and is not further expanded
>> {\}\} expands to }
>> {\\\}\} expands to \}
>>
>> —————————
>>
> Escape processing would be disabled  for anything between the  {\…\} (or 
> whatever it ends up being)

To be 100% clear: the original proposal from 2013 is not what's 
currently implemented in the Oracle JDBC driver?

That is specifically does "{\\\}\} expands to \}" no longer apply for 
this proposal? Would this instead yield "\\}" (as "{\\\}" yields "\" and 
"\}" is not an escape and thus forwarded as is?

Mark
-- 
Mark Rotteveel


More information about the jdbc-spec-discuss mailing list