From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Doug McNaught" <doug(at)mcnaught(dot)org> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Cursors and backwards scans and SCROLL |
Date: | 2003-03-10 02:33:18 |
Message-ID: | 011701c2e6ad$69d06170$6500a8c0@fhp.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
> > I'd be in favour of creating whole sets of backwards-compatibility GUC's
> > whenever we break backwards compatibility.
> >
> > eg.
> > use_72_compat = yes
> > use_73_compat = yes
>
> That sounds like a recipe for a maintenance nightmare to me.
We only have to keep them for one major version, say. eg. 7.3 release would
remove the 71_compat option...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-03-10 03:35:52 | Re: SQL99 ARRAY support proposal |
Previous Message | Doug McNaught | 2003-03-10 02:32:23 | Re: Cursors and backwards scans and SCROLL |
From | Date | Subject | |
---|---|---|---|
Next Message | jack | 2003-03-10 04:48:27 | Re: About Create Type |
Previous Message | Doug McNaught | 2003-03-10 02:32:23 | Re: Cursors and backwards scans and SCROLL |