So Micah, with my example of "Kill Bill: 2"...the search string comes to my app as
Kill Bill: 2 and I can replace the : with ":" so the search will retain the colon in the search. Awesome. Thank you for the help. On Tue, Nov 6, 2012 at 3:48 PM, Micah Dubinko <[email protected]>wrote: > Harry, > > Any strings surrounded by quotes (or whatever you've defined as the > quotation character) won't be interpreted, so colons or other syntax will > be preserved. Using a different character for the constraint joiner would > work too, of course. > > -m > > > On Nov 6, 2012, at 2:43 PM, Harry B. <[email protected]> wrote: > > > I am using search:search and the grammar options currently see the colon > (:) as the joiner-string for a constraint. The requirement has surfaced > where the query string may contain a colon and it will not be meant as a > joiner, ex. "Kill Bill:2". What should I do to accommodate this > requirement? Encoding the colon doesn't help. It seems perhaps I need to > not use the colon as a joiner and use a pipe or some other character? Any > other ideas? > > > > Thanks, > > Harry > > _______________________________________________ > > General mailing list > > [email protected] > > http://developer.marklogic.com/mailman/listinfo/general > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
