> It seems to me that postgres is trying to do as you suggest: text is
> characters and bytea is bytes, like in Java.
But the big difference is that, for text type, postgresql knows "this
is a text"
but doesnt know the encoding, as my example showed. This goes against
the concept of "text vs bytes" distintion, which per se is very useful
and powerful
(specially in this Unicode world) and leads to a dubious/clumsy string api
(IMHO, as always).
> You don't indicate what
> version you are using, this area was rejigged recently.
>
Sorry, I forget to say that my examples are for last version (8.3)
Cheers
--
Hernán J. González