Am 20.06.2010 14:39, schrieb Klaus Feichtinger:
4) I don’t know if the parser might be influenced by a
WARNING that is
generated by the postgresql daemon whenever an entry into the presentity
table is done (including XML body). From Kamailio log output I saw that
the special characters “#011” and “#012” are included in the XML body. I
guess that is the octal notation of \t (horizontal tab) and \n (newline).
However, postgresql generates an error message that looks like following:
/WARNING: nonstandard use of \\ in a string literal at character 162/
HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
Maybe this has some influence on the parser problem, too. Because in
this version of Postgresql the parameter “standard_conforming_strings”
is implicitly on – just for previous versions it could be set to off.
That means, that any backslash symbol (\) is interpreted as standard
character (no escape). Therefore the queried result of the database does
no longer include \n and \t.
I just wonder if this can be solved by storing the body as BLOB instead
of strings. Could you test using a BLOB for the body (in database and
presence modules)
regards
klaus