| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Vitali Stupin" <vitali(dot)stupin(at)ria(dot)ee>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |
| Date: | 2006-10-15 22:15:27 |
| Message-ID: | 1716.1160950527@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> I am also wondering, now that it's been raised, if we need to issue a "use
> utf8;" in the startup code, so that literals in the code get the right
> encoding.
Good question. I took care to ensure that the code strings passed to
Perl are marked as UTF8; perhaps that makes it happen implicitly?
If not, are there any downsides to issuing "use utf8"?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-10-15 22:16:31 | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |
| Previous Message | Tom Lane | 2006-10-15 22:12:43 | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-10-15 22:16:31 | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |
| Previous Message | Tom Lane | 2006-10-15 22:12:43 | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |