X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 159D15384E for ; Mon, 28 Mar 2005 03:19:47 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84694-08 for ; Mon, 28 Mar 2005 02:19:43 +0000 (GMT) Received: from flake.decibel.org (natpool.bovine.net [67.100.216.14]) by svr1.postgresql.org (Postfix) with ESMTP id 78B8052D8A for ; Mon, 28 Mar 2005 03:19:43 +0100 (BST) Received: by flake.decibel.org (Postfix, from userid 1001) id CEC26153AE; Sun, 27 Mar 2005 20:19:46 -0600 (CST) Date: Sun, 27 Mar 2005 20:19:46 -0600 From: "Jim C. Nasby" To: Tom Lane Cc: pgsql-docs@postgresql.org Subject: Re: Version information in docs Message-ID: <20050328021946.GT51784@decibel.org> References: <20050327212050.GP51784@decibel.org> <4301.1111974862@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4301.1111974862@sss.pgh.pa.us> X-Operating-System: FreeBSD 4.11-RELEASE i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.047 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/26 X-Sequence-Number: 2922 On Sun, Mar 27, 2005 at 08:54:22PM -0500, Tom Lane wrote: > "Jim C. Nasby" writes: > > ISTM it would be very useful if the docs specified what version a > > feature that would break in older versions was implemented in. The > > example that comes to mind is argument names in CREATE FUNCTION, which > > was added in 8.0. The 8.0 docs (http://lnk.nu/postgresql.org/1y3.html) > > mention the ability to name arguments, but it doesn't mention that the > > feature was added in 8.0 and can not be used in prior versions. Anyone > > who's trying to write code that will run on multiple versions of > > PostgreSQL would want to know this. > > The release notes cover that; or you can compare the docs for the oldest > and newest versions you want to work with. I think it would be more > confusing than helpful for the reference pages to try to cover all the > changes from version to version. Well, it might not need to cover all changes, just ones that might be easy to overlook. Besides, are there really that many syntax changes from one version to another? Another idea I had is that if there was actual metadata in the document source about the version info, it would be possible to output different amounts or kinds of information depending on how old the change was. For example, I doubt anyone would possibly care about changes prior to 7.0 at this point, and most people probably wouldn't care about changes prior to 7.3 or even 7.4, so the default documentation wouldn't need to show that info. Another alternative is providing a history link on features that takes you to appropriate documentation about what changes have occured and when. In this case, it would just mention that argument names first appeared in 8.0. -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"