I am using xdmp:url-encode to encode a string. While it's nice to have the feature to encode a 'space' as either '+' or '%20', I wonder if there is perhaps an undocumented feature to encode for example a '?' as either '%3f' or '%3F'. MarkLogic seems to have taken the approach of using lower-case characters. If I read RFC3986, while both lower and uppercase are to be treated as equal, they suggest for consistency that uppercase characters be used.
In my particular case, I actually have a string stored in a database that has been encoded (with the '%3F' as it was encoded by an outside tool and is stored that way in the DB). Now, when I want to query against this value, I will not get an exact match (using simple XPath expression) when encoding a passed query string parameter (using MarkLogic xdmp:url-encode). Of course, I could use cts:search and cts:element-value-query with a (case insensitive compare option), but I was curious if this question/issue has been raised in the past. Are there any plans to adjust the signature for xdmp:url-encode to support more options? Thanks. Darin. _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
