Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Re: ... and here's another change.

From: Gerald Gryschuk <ggryschuk(at)scf(dot)sk(dot)ca>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Postgres Interfaces Mailing List <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: [INTERFACES] Re: ... and here's another change.
Date: 1998-10-06 18:07:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Thomas G. Lockhart wrote:
> I'm also trying to look out for overall Postgres issues:

Well, o.k. far be it from me to argue, I'm new at this, and
come to think of it your right. The scenario I was having a
problem with only breaks down if someone adds a new odbc
source release to their Postgres distribution and than tries
to configure from the top-level Postgres ./configure. Unless
they want to watch the rest of Postgres reconfigure itself
this scenario is probably unlikely, more likely they'll just
run configure from the odbc driver directory. Of course we
should make this clear in the docs probably.

> Do you have access to the cvs tree, or should I send you a tarball? btw,
> we'll need to start exchanging patch files rather than these full
> tarballs now that we have the Postgres tree for a reference.

Unfortunately no I don't. I'm behind a firewall, don't know if that
anything but I haven't had time to even try to connect to a cvs
tree to test it.

So tarballs and patch files it is.

Gerald Gryschuk(ggryschuk(at)scf(dot)sk(dot)ca)
Programmer Analyst
Saskatoon Cancer Centre

In response to

pgsql-interfaces by date

Next:From: KaDeDate: 1998-10-07 01:01:10
Subject: re : libpq++ - getting it to work
Previous:From: Thomas HartwigDate: 1998-10-06 17:00:53
Subject: PostODBC crashes ODBC-Manager

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group