Re: Database->ServerEncoding, ClientEncoding
От | Dave Page |
---|---|
Тема | Re: Database->ServerEncoding, ClientEncoding |
Дата | |
Msg-id | FED2B709E3270E4B903EB0175A49BCB1047618@dogbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Database->ServerEncoding, ClientEncoding (Jean-Michel POURE <jm.poure@freesurf.fr>) |
Ответы |
Locale, Encoding
|
Список | pgadmin-hackers |
> -----Original Message----- > From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr] > Sent: 26 February 2002 09:44 > To: pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Database->ServerEncoding, > ClientEncoding > > > > ServerEncodingID (Long) > > ServerEncodingName (String) > I still wonder why ServerEncodingID is needed. It adds > complexity to pgSchema > without beeing used. Can't ServerEncodingID be masked? > > > ClientEncodingID (Long) > > The ClientEncodingID would be the Windows LCID (I assume that's > > relevant in this case) > To you plan to use ClientEncodingID to select fonts? What is > LCID for? My > knowledge is very little in this field. so's mine - I thought I was learning from you!! LCID is the Windows Locale ID If it's not important, ignore it. Regards, Dave.
В списке pgadmin-hackers по дате отправления: