Tom Lane t...@sss.pgh.pa.us writes:
As near as I can tell, every place where you see an explicit cast
between char * and xmlChar * is probably broken. I think we ought
to approach this by refactoring to have all those conversions go
through subroutines, instead of blithely casting.
There is
On Sunday 05 April 2009 05:00:04 Tom Lane wrote:
Chris Browne cbbro...@acm.org writes:
j...@agliodbs.com (Josh Berkus) writes:
This one is also really bad, but probably only Doc-patchable.
However, can SQL/XML really be said to be core functionality if it
only works in UTF-8?
* BUG
Peter Eisentraut pete...@gmx.net writes:
On Sunday 05 April 2009 05:00:04 Tom Lane wrote:
Is there a reason not to fix it as suggested at
http://archives.postgresql.org/pgsql-bugs/2009-02/msg00032.php
ie recode on-the-fly from database encoding to UTF8?
Probably just verifying that it works.
Peter Eisentraut pete...@gmx.net writes:
On Sunday 05 April 2009 05:00:04 Tom Lane wrote:
Is there a reason not to fix it as suggested at
http://archives.postgresql.org/pgsql-bugs/2009-02/msg00032.php
ie recode on-the-fly from database encoding to UTF8?
Probably just verifying that it works.
Chris Browne cbbro...@acm.org writes:
j...@agliodbs.com (Josh Berkus) writes:
This one is also really bad, but probably only Doc-patchable.
However, can SQL/XML really be said to be core functionality if it
only works in UTF-8?
* BUG #4622: xpath only work in utf-8 server encoding
Well,
j...@agliodbs.com (Josh Berkus) writes:
This one is also really bad, but probably only Doc-patchable.
However, can SQL/XML really be said to be core functionality if it
only works in UTF-8?
* BUG #4622: xpath only work in utf-8 server encoding
Well, much of the definition of XML assumes
