From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL odbc list" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] KSQO parameter |
Date: | 2002-06-16 09:52:45 |
Message-ID: | D85C66DA59BA044EB96AB9683819CF610150F8@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-odbc |
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)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 - there is certainly a patch outstanding that redesigns the
setup dialogues that I posted that would be affected by this...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Tedder | 2002-06-16 19:13:59 | Re: Big Test Environment Feature |
Previous Message | Bruce Momjian | 2002-06-16 00:15:40 | Caught up on email |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-06-17 01:57:56 | Re: [HACKERS] KSQO parameter |
Previous Message | Bruce Momjian | 2002-06-16 00:08:35 | Re: [HACKERS] KSQO parameter |