Dave Page wrote:
>
> > -----Original Message-----
> > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> > Sent: 16 June 2002 01:09
> > To: Tom Lane
> > Cc: PostgreSQL-development; PostgreSQL odbc list
> > Subject: Re: [ODBC] [HACKERS] KSQO parameter
> >
> > > either ... does anyone out there want to work on it?
> >
> > The following patch removes KSQO from GUC and the call to the
> > function. It also moves the main KSQO file into _deadcode. Applied.
> >
> > ODBC folks, should I remove KSQO from the ODBC driver?
>
> I'm not sure that Hiroshi has updated CVS with all our recent changes
> just yet
Sorry I've had no time to see it.
> - there is certainly a patch outstanding that redesigns the
> setup dialogues that I posted that would be affected by this...
I don't object to remove the KSQO option at server side.
But why must the option be removed from the odbc driver
together ? As I mentioned many many times, the driver
isn't only for the recent (especially not yet released)
version of servers. I think we had better have a separate
dialog for obsolete options.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
