Re: ODBC and encodings problem

I've looked at the mylog outputs from pgODBC in this case and they seem to
show the driver (at some point) returns the correct values. How these are
then translated and shown in MS Access is beyond me. I'll keep
investigating though.

[investigated some more]I just tried pgODBC 7.03.0208 and I get the correct
result. Seems it's another bug that's been introduced after this time.
I'll look to see which version is the earliest to cause this problem.

Ben

""Philippe Lang"" <philippe(dot)lang(at)attiksystem(dot)ch> wrote in message
news:6C0CF58A187DA5479245E0830AF84F42143227(at)poweredge(dot)attiksystem(dot)ch(dot)(dot)(dot)
> There is a project of an ODBC driver that uses libpq at Command Prompt...
>
> This is an answer I got a few weeks ago.
>
>> Our driver is sorely outdated. We are currently working on a brand new
>> (as in from scratcH) open source driver sourced from libpq.
>>
>> Sincerely,
>>
>> Joshua D. Drake
>> Command Prompt, Inc.
>
> We are all looking forward to trying it. But licencing and deadlines are
> not really clear at the moment.
>
> Philippe
>
>
> -----Message d'origine-----
> De : pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] De la part de Ben Trewern
> Envoy : vendredi, 15. avril 2005 13:15
> : pgsql-odbc(at)postgresql(dot)org
> Objet : Re: [ODBC] ODBC and encodings problem
>
> Does this mean I have to initdb my cluster again? I tried to do this on
> windows with 'initdb --encoding=LATIN1' but it hang on 'selecting default
> max_connections ...' I'm looking into this now. Not sure if it's an
> encoding problem or something else.
>
> What I was wondering was, why does the ODBC driver act differently to Zeos
> or pgAdmin III? Zeos and pgAdmin both use the libpq client library which
> I suppose is the standard. Is there a way the ODBC driver could be hacked
> to give the same response as libpq or am I simplifying this too much.
>
> Ben
>
> ""Philippe Lang"" <philippe(dot)lang(at)attiksystem(dot)ch> wrote in message
> news:6C0CF58A187DA5479245E0830AF84F4214321E(at)poweredge(dot)attiksystem(dot)ch(dot)(dot)(dot)
>> Hi,
>>
>> I don't know exactly which encoding you need, but at least for french,
>> encoding a datatabase in LATIN1 solves the problem...
>>
>> Bye
>>
>> Philippe
>>
>> -----Message d'origine-----
>> De : pgsql-odbc-owner(at)postgresql(dot)org
>> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] De la part de Ben Trewern
>> Envoy : jeudi, 14. avril 2005 21:20 : pgsql-odbc(at)postgresql(dot)org
>> Objet : [ODBC] ODBC and encodings problem
>>
>> Hi all,
>>
>> Using PostgreSQL 8.0.1 on Linux
>>
>> I've got a database with an encoding of SQL_ASCII. I've accessed it
>> with pgAdmin III and Delphi through ZeosDBO and had no problems. Now
>> I've been using MS Access XP with pgODBC version 8.00.0101 to connect
>> to it with some success till now. I've noticed that any field with a
>> sign in it is not displaying correctly, I get 'WO ,658.06' instead of
>> 'WO 4,658.06'
>> and 'WO 60.56' instead of 'WO 128.88' etc. I assume it's something
>> to do with the encodings used server side or client side.
>>
>> Any ideas how to fix this?
>>
>> Regards,
>>
>> Ben
>>
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 8: explain analyze is your friend
>>
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 5: Have you checked our extensive FAQ?
>>
>> http://www.postgresql.org/docs/faq
>>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>