Re: Database->ServerEncoding, ClientEncoding - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Database->ServerEncoding, ClientEncoding
Date
Msg-id FED2B709E3270E4B903EB0175A49BCB1047618@dogbert.vale-housing.co.uk
Whole thread Raw
In response to Database->ServerEncoding, ClientEncoding  (Jean-Michel POURE <jm.poure@freesurf.fr>)
Responses Locale, Encoding  (Jean-Michel POURE <jm.poure@freesurf.fr>)
List 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 by date:

Previous
From: Dave Page
Date:
Subject: Re: fake vs real CREATE OR REPLACE VIEW
Next
From: Jean-Michel POURE
Date:
Subject: Re: Database->ServerEncoding, ClientEncoding