Re:
| От | Hiroshi Saito |
|---|---|
| Тема | Re: |
| Дата | |
| Msg-id | 02a701c3884a$b7a6df70$1f324d80@w2k обсуждение исходный текст |
| Ответ на | Re: ("Serguei A. Mokhov" <mokhov@cs.concordia.ca>) |
| Список | pgadmin-hackers |
From: "Andreas Pflug" <pgadmin@pse-consulting.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
В списке pgadmin-hackers по дате отправления: