I have discovered that XPost will return an Error if the key value includes a parenthesis.
Example -  Bob Jones (Home)
For some reason it does not recognize a match when there is a parenthesis.
I can find no documentation on this. Is it a bug?

Thank you

Hello Jon,

Looking at your database the problem is not the parenthesis alone it is the combination of the ^ character and the parenthesis that is causing the XPost to fail. If you replace the ^ character which you are using to keep data separate with another character you will be fine.

From what I understand of your application, you may want to look into passing a unique identifier in along with the rest of the data. ex.  12:04^Bob Smith (Home)^123  In this case 123 is the unique key for the record that you selected and you can use 123 in the XPost instead of passing 12:04^Bob Smith (Home) through the XPost.

That is the recommended way, but if it doesn't work for you I believe of all the single characters that you could pass the pipe '|' character is probably the safest.

-Ray

Quote:


I'm not sure it isn't a bug. A lot of characters are significant to Q&A search syntax, and an equally large set are significant to regular expression syntax. Sesame translates Q&A syntax into a regular expression and passes that to a regex parser which compiles it and uses the result to evaluate the "match". It may be failure on my part to eliminate this particular pre-existing reg-ex construct before the search string gets parsed by the regex compiler. It may be that this is one combination that was simply not anticipated within the parser when trying to perform the match. Usually, "^" is the start of line anchor match character and parenthesis group binary expression to affect evaluation order.

In regex, you can say:
^M.*B$

To mean: find a string that starts at the start of line with M and ends with B at the end of the line, with anything inbetween.

Perhaps this XPost issue needs to be looked at more closely. Upon further testing, I have found that Xpost does not behave as expected with certain characters, including the "|" (pipe).
I spent an entire day on this, devising workarounds, etc. only to finally discover the problem was the pipe. In my test, the XPost does not fail, yet if there is a pipe in the string, it posts wrong values. Get rid of the pipe, and everything is perfect.
I am using the pipe with no other symbols. Wrong values are posted depending on the order in which the posts happen. Very strange...

--Jon