Skip site navigation (1) Skip section navigation (2)

Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text

From: Marc Herbert <Marc(dot)Herbert(at)continuent(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text
Date: 2006-03-31 19:12:13
Message-ID: khjodzmig36.fsf@meije.emic.fr (view raw or flat)
Thread:
Lists: pgsql-odbc
Johann Zuschlag <zuschlag2(at)online(dot)de> writes:

> I've read about the problems with the NULL bytes on Unix machines.

This problem is not related to Unix at all but to the programming
language used. Most standard C functions use the zero byte convention
as a string terminator, so it becomes a forbidden character in C.

On the other hand String objects in C++ and Java use a separate length
field, and having NULLs inside a string is a no brainer there.

The ODBC API has been designed for C and Cobol. Cobol does not forbid
zero as a character either. When browsing the ODBC spec you'll notice
it carefully caters for the two ways.


Guess which programming language is used PostgreSQL.


I suspect unicode does not care at all about this. After all unicode
is just about characters not about strings.




In response to

Responses

pgsql-odbc by date

Next:From: Bart SamwelDate: 2006-04-01 01:26:58
Subject: Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text
Previous:From: Marc HerbertDate: 2006-03-31 19:02:38
Subject: Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group