loper Discussion
Subject: Re: [MarkLogic Dev General] Question about xdmp:url-encode
You might also just need fn:encode-for-uri, which produces upper case hex
digits. Depending on the source of the data, I might be concerned about the
risk of variation in the set of reserved characters though. I'
You might also just need fn:encode-for-uri, which produces upper case hex
digits. Depending on the source of the data, I might be concerned about the
risk of variation in the set of reserved characters though. I'd probably lean
towards comparing to a decoded copy of the string, stored with or
Darin, have you considered setting a case-insensitive collation? That should
work for an XPath expression.
-- Mike
On Dec 9, 2010, at 17:35, "McBeath, Darin W (ELS-STL)"
wrote:
>
> I am using xdmp:url-encode to encode a string. While it's nice to have the
> feature to encode a 'space' as e
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-
