Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by postgresql.org (Postfix) with ESMTP id 69361475ADD for ; Mon, 4 Mar 2002 02:51:55 -0500 (EST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g247pnk73214; Mon, 4 Mar 2002 20:51:50 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200203040751.g247pnk73214@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: Janning Vygen Date: Mon, 4 Mar 2002 02:51:47 -0500 MIME-Version: 1.0 Subject: Re: [SQL] thinking about versioning my database schema Reply-To: dan@langille.org Cc: pgsql-admin@postgresql.org In-reply-to: <200203040710.g247AOj05681@janning.planwerk6.local> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200203/31 X-Sequence-Number: 3566 On 4 Mar 2002 at 8:10, Janning Vygen wrote: > So i am saving the schema version inside the databse. Is it a good > idea? or is it nonsens and there is a much better way how to do it? I have a system table. One of the fields is the database version. If I change the schema, I modify the version. The applications knows what version it can run with. If it finds an older version, it reports this ot the user and suggests they upgrade their database. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples