Обсуждение: installing/running ODBC

Поиск
Список
Период
Сортировка

installing/running ODBC

От
Laurel Williams
Дата:
Hello all,

I know there is a Postgres-ODBC listserv, but I have the feeling this is a
blindingly obvious question and thus this is the best place to put it.

I'm trying to connect to my PostgreSQL database (7.1beta4, running on Red
Hat 6.2) from a Windows client machine. I understand the Windows side of
setting up a DSN, etc. (and the relevant software one needs to download),
but what exactly needs to be running/installed on the Linux side?
PostgreSQL was compiled --with-odbc ... now what? I have read the
documentation in the Programmer's Guide which mentions iODBC/Openlink
Software. When I download the iODBC software, the software seems incomplete
and the documentation is very confusing (as opposed to unixODBC, which
unfortunately I gather is not an option here?). There is a more complicated
commercial-type software from Openlink which is available for small
noncommercial applications--should I be using that instead? It doesn't help
that I am new to ODBC, too, and I feel that I may be missing the point here.

Also, I read a post on the pgsql-odbc list which said that one had to use
both a user and password with ODBC and modify pg_hba.conf. The poster said
"crypt" did not work for them. Should I expect "trust" to work or might
this also encounter problems?

Thanks in advance for anyone who can help.

Cheers,

Laurel Williams
tech@clearwater-inst.com
Watertown, MA


Re: installing/running ODBC

От
Louis Bertrand
Дата:
I don't believe you need to compile anything special on the Linux side.
The Windows ODBC driver is able to communicate with the PostgreSQL
backends in "native" dialect.

You need to start postmaster with -i to tell it to listen on the network
(netstat -a  and look for a LISTEN on port 5432 to check)
You also need to make sure pg_hba.conf in your data directory enables
remote hosts to connect (hosts or entire subnets).

On the Windows side of things (tried it Friday on Win98):
 get the iodbc driver from ftp.postgresql.org
 install it on your Windows box
 Start > Settings > Control panel > ODBC32
   Add a machine DSN for your PostgreSQL server.
A few gotchas: the default is read-only. Look in the Advanced... and
Options... subpanels. The log files are under the C:\ folder by
default. Look there for clues.

I tried it from Access 2000, using the File > Import Data > Link tables
You need to select ODBC sources as the file type.

Ciao
 --Louis  <louis@bertrandtech.on.ca>


On Fri, 16 Mar 2001, Laurel Williams wrote:

> Hello all,
>
> I know there is a Postgres-ODBC listserv, but I have the feeling this is a
> blindingly obvious question and thus this is the best place to put it.
>
> I'm trying to connect to my PostgreSQL database (7.1beta4, running on Red
> Hat 6.2) from a Windows client machine. I understand the Windows side of
> setting up a DSN, etc. (and the relevant software one needs to download),
> but what exactly needs to be running/installed on the Linux side?
> PostgreSQL was compiled --with-odbc ... now what? I have read the
> documentation in the Programmer's Guide which mentions iODBC/Openlink
> Software. When I download the iODBC software, the software seems incomplete
> and the documentation is very confusing (as opposed to unixODBC, which
> unfortunately I gather is not an option here?). There is a more complicated
> commercial-type software from Openlink which is available for small
> noncommercial applications--should I be using that instead? It doesn't help
> that I am new to ODBC, too, and I feel that I may be missing the point here.
>
> Also, I read a post on the pgsql-odbc list which said that one had to use
> both a user and password with ODBC and modify pg_hba.conf. The poster said
> "crypt" did not work for them. Should I expect "trust" to work or might
> this also encounter problems?
>
> Thanks in advance for anyone who can help.
>
> Cheers,
>
> Laurel Williams
> tech@clearwater-inst.com
> Watertown, MA
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>