pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jorge Silva <jorge.silva93@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: xPath in a database with LATIN1 encoding
Date: Sat, 24 Apr 2021 15:20:43 -0300
Message-ID: <09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com> (raw)
In-Reply-To: <1707307.1619282961@sss.pgh.pa.us>
References: <E8EDD295-7797-4EC7-9F60-96A9554CDEE6@gmail.com>
	<1707307.1619282961@sss.pgh.pa.us>

Thanks for the quick reply, Tom. I am trying something simpler. I am trying to find a way to run the xPath function with a xml file type, which has latin characters, such as:
SELECT xpath(‘//xml_test/text()’, convert_from(convert_to(‘<xml_test>çã</xml_test>','utf-8’),'utf-8')::xml)

This line returns the same error, as follows:
[Code: 0, SQL State: 2200M]  ERROR: could not parse XML document
  Detail: line 1: Input is not proper UTF-8, indicate encoding !
Bytes: 0xE7 0xE3 0x3C 0x2F
<xml_test>çã</xml_test>
          ^
This happens because the “text”, which is the output from convert_from() function is encoded with LATIN1, the database encoding set, and not UTF-8.  Is there a way that a text variable is not encoded as the database encoding set, but some other encoding set, such as UTF-8? From what I’ve searched for, it seems that it would be something similar to nvarchar that only exists in Microsoft SQL Server.



> On 24 Apr 2021, at 13:49, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Jorge Silva <jorge.silva93@gmail.com> writes:
>> The characters that it is not recognizing are both “ç” and “ã” because I think they are encoded differently in latin1 and utf-8. Is it possible to somehow use the xPath function with special characters in the XML and in a database which is not encoded with utf-8? 
> 
> I don't have a lot of expertise in this area, but I think you need
> an explicit encoding indicator in the xml header, a la
> 
>    <?xml encoding="latin1"?> ...
> 
> On the whole, the xml type is definitely easier to use with database
> encoding set to utf8.  I think you'll be paying for encoding conversion
> every time we interact with libxml, for instance.
> 
> 			regards, tom lane

view thread (6+ messages)  latest in thread

Message-ID: <09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com>
Permalink:  ../09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com/
Also on:    postgresql.org/message-id/09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jorge.silva93@gmail.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
  Subject: Re: xPath in a database with LATIN1 encoding
  In-Reply-To: <09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox