| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Reinhard Max <max(at)suse(dot)de> |
| Cc: | Vsevolod Lobko <seva(at)sevasoft(dot)kiev(dot)ua>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Patch for pl/tcl Tcl_ExternalToUtf and Tcl_UtfToExternal |
| Date: | 2001-09-06 10:30:21 |
| Message-ID: | Pine.LNX.4.30.0109061229180.823-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Reinhard Max writes:
> So basically there are two possibilities:
>
> a) Patch pl/tcl and PgTcl to do the code conversion, but do it right
> by using the Database's encoding instead of Tcl's system encoding.
>
> b) Require databases to be in UNICODE if they are to be accessed
> from Tcl >= 8.1 so that the strings that come out of the database
> are already UTF-8.
Could you summarize how that affects the proposed patch? (The patch is
already in, but I'm still not sure if it's not just an arbitrary
workaround.)
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vsevolod Lobko | 2001-09-06 10:33:53 | Re: Patch for pl/tcl Tcl_ExternalToUtf and Tcl_UtfToExternal |
| Previous Message | Peter Eisentraut | 2001-09-06 10:21:58 | Re: Bug in createlang? |