Postgres and chinese, korean, japanese charsets
| From: | Alberto Serra | Date: | Tue, 09 Jul 2002 06:09:50 +0000 |
| Subject: | Postgres and chinese, korean, japanese charsets | ||
| References: | 1 2 3 4 5 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-106244@lists.php.net to get a copy of this message | ||
Привет!
Jean-Christian Imbeault wrote:
Alberto Serra wrote:Can anyone say something about this? It would mean that a content repository ported to Postgres would not be able to hold chinese, korean and japanese content at the same time. Quite a big minus, I'd say. Any chinese, korean or japanese programmers on this list? (I put the countries list in alphabetical order, no personal preferences implied). Пока Альберто Киев @-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@ LoRd, CaN yOu HeAr Me, LiKe I'm HeArInG yOu? lOrD i'M sHiNiNg... YoU kNoW I AlMoSt LoSt My MiNd, BuT nOw I'm HoMe AnD fReE tHe TeSt, YeS iT iS ThE tEsT, yEs It Is tHe TeSt, YeS iT iS ThE tEsT, yEs It Is.......I hope you mean one charset per language. Otherwise I can just cancel POstgres from my list of usable engines. But yes, it can't be just one.I'm no pgsql expert but I think that yes, it will only accept input in one charset. But for charsets that use only 8-bits I think you can insert data that is in more than one charset. But for charsets that use more than 8-bits I think pgsql actually checks that the input is in the charset the DB expects it to be in.