I recently upgraded my DB from 7.4.3 to 8.0.4 and I've noticed the following errors appearing in my serverlog:
2005-11-03 05:56:57 CST 127.0.0.1(38858) ERROR: Unicode characters greater than or equal to 0x1 are not supported
2005-11-03 06:04:09 CST 127.0.0.1(38954) ERROR: invalid byte seque
Hi,
I am trying to convert from SQL_ASCII to UNICODE.
I have a program that will read from a table in one database
and write to a table in a different database.
I am hoping this all I need do (One data base is SQL_ASCII and
the other is UNICODE).
I get a byte sequence error writi
Ain't trying to prove no one no thing.
So sorry.
Thamks.
On Sunday 08 May 2005 19:43, you wrote:
> Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes:
> >> If you're still using a PostgreSQL version that has the --enable-locale
> >> option then you rather need to upgrade.
> >
> > And
Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes:
>> If you're still using a PostgreSQL version that has the --enable-locale
>> option then you rather need to upgrade.
> And excuse me ?
> [EMAIL PROTECTED] postgresql-8.0.2]# ./configure --enable-locale
> checking build system type...
Hi,
And excuse me ?
[EMAIL PROTECTED] postgresql-8.0.2]# ./configure --enable-locale
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking which template to use... linux
checking whether to build with 64-bit integer date/time support...
BR,
Aarn
Aarni Ruuhimäki wrote:
> You might also want (re?)configure your Pg-system with
> --enable-locale and set your preferred locale and db default encoding
> in initdb to suit your needs, in order to have alphabetical sortings
> etc. work ok.
If you're still using a PostgreSQL version that has the --e
Hi,
In my experience , I think your best bet and an all-around good general
encoding to use is latin1, which copes with l'accent egys & graves, umlauts,
harasoos and others.
Not so sure about the M$-import stuff though. Or asp or .net. Read the Gates
Private Licence ...
You might also want (r
I am not clear on what makes this work?
I am going live Sunday and have thus far been using SQL_ASCHII.
I still have the feeling I should be using something else,
but when I used Unicode my conversion from MSSQL blew up on encoding error for
a char that wasn’t plain ASCHII(IE French or
On Thursday 08 April 2004 10:32, kumar wrote:
>
> create table encodeco(c1 int4, c2 int4);
> insert into encodeco values(1, 2);
> select * from encodeco;
>
> So I want to encode the data while selecting.
> select encode(c1,'base64') from encodeco;
> So i tried
> select encode('c1','ba
Dear Friends,
Postgres 7.3.2 on Linux 8
I would like to fetch the datas from a table in a
encoded format.
create table encodeco(c1 int4, c2 int4);insert
into encodeco values(1, 2);select * from encodeco;
So I want to encode the data while
selecting.
select encode(c1,'base64')
O kyrios Joe Conway egrapse stis Mar 3, 2004 :
> Achilleus Mantzios wrote:
>
> > is there a way to encode a bytea in such a way that the resulting
> > text stream be readily available (\\ escaped for unprintable chars) for
> > usage in an insert statement?
> >
> > None of base64,hex,escape opti
Achilleus Mantzios wrote:
is there a way to encode a bytea in such a way that the resulting
text stream be readily available (\\ escaped for unprintable chars) for
usage in an insert statement?
None of base64,hex,escape options in encode() seem to produce
anything close.
This is meant to be used
Hi,
is there a way to encode a bytea in such a way that the resulting
text stream be readily available (\\ escaped for unprintable chars) for
usage in an insert statement?
None of base64,hex,escape options in encode() seem to produce
anything close.
This is meant to be used with generating inser
13 matches
Mail list logo
