[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [cmis] Groups - cmis-spec-v1.0e1-draft.doc uploaded
Thanks Ryan for pointing back to the source, this helps. Am I correct that we have excluded a syntax change for the errata, because this would break compatibility? This means we still have to follow the double escaping rules. I think beside the example some more text would be helpful mentioning that: · For CONTAINS double escaping needs to be performed (CMIS escaping for text search expressions according to 2.1.10.3 and SQL escaping to get a valid character string literal) · We should state the order in which both escapings have to be performed (e.g. first CMIS escaping, then SQL escaping) · Have the example If I follow these rules I come to the following conclusion: That’s -> That\’s // CMIS Escaping rule by backslashes according to section 2.1.10.3 of the spec That’\s -> That\’’s // SQL escaping rule, double a single quote That\’’s -> ‘That\’’s ‘ // put single quotes around it to get a valid SQL character string literal Where is the point where I am wrong? Looking back at CMIS-660 It seems that we first discussed a syntax change that we later have postponed to a later spec revision. It might be possible that we still have some uncertainties what we actually see in place for 1.0. Jens From: Ryan McVeigh [mailto:rmcveigh@ziaconsulting.com] Jens, This was taken from the comments of CMIS-660, specifically Florent's comment. If the doc isn't clear yet, we haven't successfully generated our errata. :) Let me know if after reading Florent's comment if this makes sense and how we can further clarify. Thanks, -Ryan On Wed, Jan 19, 2011 at 10:41 AM, Jens Hübel <jhuebel@opentext.com> wrote: I have a question regarding
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]