Re: Usind database with encoding UNICODE and vovel

Dave, thanks 4 your time;
* I've installed MDAC 2.8 with same results.

* If I don't set locale on the client it doesn't work, pgadmin either
(show wrong encoding data)

After connect trough odbc:
SHOW CLIENT_ENCODING;
return -> UTF8

The same command after connect to the LATIN10 db on pgadmin;
SHOW CLIENT_ENCODING;
return -> UNICODE

Try create a LATIN10 db and connect to it to return client encoding.

* About MsQuery I was speaking about visual querys design time, not to
return millons of records.
It works fine with other db, because it find the fields to make the
relationship between tables, right now I'm migrating an app from mysql
to postgres, the same querys, same data on msquery with mysql (myodbc)
works fine; with psqlodbc hangup trying to relate tables (on visual
design, without return a single record), If I type the query it works,
but don't expect final users write a sql sentence =)

* What about the 2 chars used to store strange chars?

Thanks again and again.
Alejandro

2005/8/4, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>:
>
>
> > -----Original Message-----
> > From: Alejandro D. Burne [mailto:alejandro(dot)dburne(at)gmail(dot)com]
> > Sent: 04 August 2005 14:13
> > To: Dave Page
> > Subject: Re: Usind database with encoding UNICODE and vovel
> >
> > Ok, XP/MDAC 2.5
>
> 2.5 is quite old now - the current is 2.8 sp1 iirc
>
> > I'll be testing now with 08.01.0003; my first word is works, "but"
> > this strange chars use 2 chars internally in the string
> > SET CLIENT_ENCODING = 'LATIN10';
> > INSERT INTO prueba VALUES ('ÑAÑA');
> > SELECT * FROM prueba;
> > returns 'ÑAÑA' <- WORKS OK
> >
> > just for test..
> > SET CLIENT_ENCODING = 'UNICODE';
> > SELECT * FROM prueba;
> > returns 'A?AA?A' <- 6 chars
>
> In all my testing, I found no need to execute SET CLIENT_ENCODING at all. Please try it without.
>
> > Another tip =)
> > MsExcel returns wrong data.
> > The problem seems to be the client don't select the right encoding for
> > the DB, in this case LATIN10 and I don't know the way (if I can) to do
> > this.
> >
> > The last one... in MsExcel (I guess MsQuery) when I try to relate 2
> > tables don't recognize related fields, with small tables there is no
> > problem but with millon of records the app wait for a long time to
> > stablish manually the relation.
>
> That is to be expected - millions of records is a lot of work for any driver!
>
> Regards, Dave.
>