Re:

From: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re:
Date: 2003-10-01 18:34:58
Message-ID: 02a701c3884a$b7a6df70$1f324d80@w2k
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

From: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>

> Hiroshi Saito wrote:
(snip)
> >It isn't understood.
> >Shouldn't put it in SQL_ASCII.
> >Database comes to return the result which made a mistake.
> >Or, do you use 256(2^8=256) ASCII?
> >
>
> The DB will store 8 bit per character, regardless of the db encoding.
> When it comes to conversion, only 7 bits are valid, if you tell the
> backend "this is ASCII data". Your fault, if it actually isn't.

However,
WHERE of SELECT will go to look for it with 7bit for ENCODING if to be SQL_ASCII.
Then, it fails.
And, order by, too.
Therefore, it is the case which you must not use.

regards,
Hiroshi Saito

In response to

  • Re: at 2003-10-01 18:28:44 from Andreas Pflug

Browse pgadmin-hackers by date

  From Date Subject
Next Message Andreas Pflug 2003-10-01 18:37:39 Re: utffile.cpp & expatd.lib
Previous Message Andreas Pflug 2003-10-01 18:32:20 Re: