Re: ODBC and encodings problem - Mailing list pgsql-odbc
From | Philippe Lang |
---|---|
Subject | Re: ODBC and encodings problem |
Date | |
Msg-id | 6C0CF58A187DA5479245E0830AF84F42143227@poweredge.attiksystem.ch Whole thread Raw |
In response to | ODBC and encodings problem ("Ben Trewern" <ben.trewern@mowlem.com>) |
List | pgsql-odbc |
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@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] De la part de Ben Trewern Envoyé : vendredi, 15. avril 2005 13:15 À : pgsql-odbc@postgresql.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 hangon 'selecting default max_connections ...' I'm looking into this now. Not sure if it's an encoding problem or somethingelse. What I was wondering was, why does the ODBC driver act differently to Zeos or pgAdmin III? Zeos and pgAdmin both use thelibpq client library which I suppose is the standard. Is there a way the ODBC driver could be hacked to give the sameresponse as libpq or am I simplifying this too much. Ben ""Philippe Lang"" <philippe.lang@attiksystem.ch> wrote in message news:6C0CF58A187DA5479245E0830AF84F4214321E@poweredge.attiksystem.ch... > 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@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org] De la part de Ben Trewern > Envoyé : jeudi, 14. avril 2005 21:20 À : pgsql-odbc@postgresql.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@postgresql.org
pgsql-odbc by date: