| From: | Dennis Björklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Character encoding |
| Date: | 2003-06-10 20:22:42 |
| Message-ID: | Pine.LNX.4.44.0306102205440.32515-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 10 Jun 2003, Peter Eisentraut wrote:
> we should try to keep the (translated) column headers within the client,
> to side-step this issue. Do you want to investigate that?
That is the obvious solution, there is no real need to send the strings to
the server in the first place.
The problem is not just with column headers though as it's also used in
the data in the table. (which of course has the same solution, examin the
data when it get to the client and substitute for the translated string).
I'll take a look at it and probably fix it by the weekend (if not sooner).
--
/Dennis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-06-10 20:57:24 | Re: Re-ordering .CONF params ... questions for this list |
| Previous Message | Joe Conway | 2003-06-10 20:05:14 | Re: Re-ordering .CONF params ... questions for this list |