| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: compiler warnings in ODBC |
| Date: | 2001-11-04 10:41:33 |
| Message-ID: | 3BE51B5D.5ED0FA62@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>
> Hiroshi Inoue writes:
>
> > ISTM neither you nor Philip Warner would use the driver
> > in reality. I'm suspicious if --enable-odbc has a meaning
> > without the environment. We could have 3 kind of ODBC
> > drivers under unix now.
> > 1) stand-alone driver made with --enable-odbc.
> > 2) iODBC driver made with --with-iodbc.
> > 3) unixODBC driver made with --with-unixODBC.
> >
> > Because they are exclusive, it seems to have little meaning
> > to make 1) in advance. In addition it seems misleading if
> > people would regard 1) as the standard PG driver.
>
> It probably doesn't make the greatest possible sense, but it's backward
> compatible and consistent with typical configure options.
>
> Btw., to get the iODBC driver, you need both options --with-iodbc and
> --enable-odbc. If you only use the former, you get nothing at all.
> Again, this could conceivably be done differently.
--enable-odbc=standalone
--enable-odbc=iODBC
--enable-odbc=unixODBC
could be the logical way to do it ?
----------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-11-04 13:04:20 | Re: compiler warnings in ODBC |
| Previous Message | Bruce Momjian | 2001-11-04 07:04:10 | Re: "ADD" notice in CREATE/ALTER TABLE |