Re: WIN1250 as server encoding
| От | Tom Lane |
|---|---|
| Тема | Re: WIN1250 as server encoding |
| Дата | |
| Msg-id | 4038.1095261688@sss.pgh.pa.us обсуждение |
| Ответ на | WIN1250 as server encoding (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: WIN1250 as server encoding
|
| Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes:
> Some people have requested to add WIN1250 as an allowed server encoding.
> So far, the order of the encoding numbers determined which ones were
> client-only, so in order not to renumber the encodings, I could only
> come up with the attached ugly solution. If no one thinks of a better
> one, we'll go with that.
Can't we just renumber them?
AFAIR, the only place where these numbers are stored is in
pg_database.datencoding, so only the server-encoding values are frozen
in any meaningful sense. You could rearrange the numbers currently
assigned to client encodings to preserve the range property.
regards, tom lane
В списке pgsql-hackers по дате отправления: