Re: A proper fix for the conversion-function problem
This is a discussion on Re: A proper fix for the conversion-function problem within the pgsql Hackers forums, part of the PostgreSQL category; --> > Are there any encodings we care about that require embedded zero bytes? UTF-8 does! ---------------------------(end of broadcast)--------------------------- TIP ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-11-2008, 04:43 AM
| ||||
| ||||
 Re: A proper fix for the conversion-function problem > Are there any encodings we care about that require embedded zero bytes? UTF-8 does! ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org      |
|
04-11-2008, 04:43 AM
| |||
| |||
| Re: A proper fix for the conversion-function problem On 2005-05-04, "John Hansen" <john@geeknet.com.au> wrote: >> Are there any encodings we care about that require embedded zero >> bytes? > > UTF-8 does! nonsense -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services |
|
04-11-2008, 04:43 AM
| ||||
| ||||
| Re: A proper fix for the conversion-function problem "John Hansen" <john@geeknet.com.au> writes: >> Are there any encodings we care about that require embedded zero > bytes? > UTF-8 does! Surely not. Were you thinking of UTF-16 or UCS-2 or whatever it's called? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
Linear Mode
