On Thursday 24 June 2010, Klaus Feichtinger wrote: > Yes - from (subscriber) user agents point of view it "solves" the original > problem. Now each Notify message (except the Subscribe confirmance > notifications) include PIDF bodies. > > But as written on Monday, kamailio still produces the internal error > messages that look the same as before: > > ERROR: presence_xml > [notify_body.c:515]: while parsing xml body message > > ERROR: presence_xml > [notify_body.c:84]: while aggregating body > > I think this should be clarified / tested.... > > > That sounds more complex and we still have to use the E'' prefix. I > > think it would be easier to just add the E'' prefix to the current code. > > > > But now I wonder what data type is used currently - the recent bug > > report on the bug-tracker mentions problems with BLOB, which would > > indicate that the body is already saved as BLOB. > > > > IIRC you said you already tried adding the E'' prefixes to the > > db_postgresql code. Does this, together with the \0 patch from the > > bug-tracker solve your problems?
Hi Klaus, i've commited the null-termination patch to the repository. Do you've also a patch for this escaping issue? Did i understand it correctly that its a generic issue for all BLOB users on postgres? Cheers, Henning _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
