On 2019-03-17 15:01:40 +, Warner, Gary, Jr wrote:
> Many of us have faced character encoding issues because we are not in control
> of our input sources and made the common assumption that UTF-8 covers
> everything.
UTF-8 covers "everything" in the sense that there is a round-trip from
each ch
Many of us have faced character encoding issues because we are not in control
of our input sources and made the common assumption that UTF-8 covers
everything.
In my lab, as an example, some of our social media posts have included ZawGyi
Burmese character sets rather than Unicode Burmese. (Bec
On 3/15/19 11:59 AM, Gunther wrote:
> This is not an issue for "hackers" nor "performance" in fact even for
> "general" it isn't really an issue.
As long as it's already been posted, may as well make it something
helpful to find in the archive.
> Understand charsets -- character set, code point,
uot;special
characters". My own people get that same sermon from me when they make
that mistake.
-Gunther
On 3/15/2019 1:19, M Tarkeshwar Rao wrote:
Hi all,
Facing issue in using special characters. We are trying to insert
records to a remote Postgres Server and our application not ab
On Thursday, March 14, 2019, M Tarkeshwar Rao
wrote:
>
> Facing issue in using special characters. We are trying to insert records
> to a remote Postgres Server and our application not able to perform this
> because of errors.
>
> It seems that issue is because of the special c
Hi all,
Facing issue in using special characters. We are trying to insert records to a
remote Postgres Server and our application not able to perform this because of
errors.
It seems that issue is because of the special characters that has been used in
one of the field of a row.
Regards
