| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | jm(at)poure(dot)com |
| Cc: | Hiroshi Saito <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: |
| Date: | 2003-10-01 18:21:31 |
| Message-ID: | 3F7B1B2B.8040402@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Jean-Michel POURE wrote:
>Le Mercredi 1 Octobre 2003 20:05, Andreas Pflug a écrit :
>
>
>>This is not a bug of PostgreSQL, nor of pgAdmin.
>>SQL_ASCII database *should* contain only 7bit ascii characters. If you
>>use 8-bit characters, conversion is unpredictable (well, it *is*
>>predictable, but probably not what you'd like to see)
>>
>>
>
>IMHO, SQL_ASCII database contain more than 7bit characters. I used it several
>times to store Frenc accentuated text and it worked like a charm. The name
>"ASCII" may not be well chosen. It contains more than ASCII presently.
>
>
>
It's no problem storing non-UTF characters in an UNICODE database
either, you will never notice until you try to convert.
Misusing the database is not a good idea on the long run.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-10-01 18:26:03 | Re: pgAdmin III under wxCocoa |
| Previous Message | Hiroshi Saito | 2003-10-01 18:17:33 | Re: |