From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16672 invoked by alias); 6 Mar 2003 15:22:29 -0000 Mailing-List: contact rhdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: rhdb-owner@sources.redhat.com Received: (qmail 16664 invoked from network); 6 Mar 2003 15:22:27 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 6 Mar 2003 15:22:27 -0000 Received: from redhat.com (toddnrodd.toronto.redhat.com [172.16.14.62]) by touchme.toronto.redhat.com (Postfix) with ESMTP id D981F80001E; Thu, 6 Mar 2003 10:22:26 -0500 (EST) Message-ID: <3E6767B2.7030205@redhat.com> Date: Thu, 06 Mar 2003 15:22:00 -0000 From: Patrick Macdonald User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jonathan Sand Cc: rhdb@sources.redhat.com Subject: Re: postgresql 7.3 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00049.txt.bz2 Hi Jonathan, We will be providing a PostgreSQL - Red Hat Edition iso towards the end of April. However, it will contain pristine PostgreSQL 7.3.x community binaries/source. You may want to download the current rpms from Red Hat which are already at this level. Cheers, Patrick Jonathan Sand wrote: > can you give me an approximate timeframe for redhat's release of rhdb > based on postgresql 7.3? > > my problem is that I'm using redhat bugzilla 2.15 with a database > created with bugzilla based on mysql. I've managed to transfer the data > out of mysql and into postgres (no small feat), and bugzilla runs, but > it has a few bugs. I've, since then, downloaded redhat bugzilla 2.17, > only to discover that the schema expected in this version are quite > different. among the many changes, one of them can't be performed by > rhdb 2.1 (postgresql 7.2.3). > > specifically: several of the tables contain essentially identical data > (eg, products.value and bugs.product) with data type varchar. this being > inefficient as a primary key and foreign key, these column definitions > are being replaced by integer primary keys and integer references, > respectively. postgres 7.3 allows the following sql: > > alter table products add id int; > ... set new unique values in this new id column .... > alter table products alter id set not null; > alter table products add primary key(id); > > postgresql 7.2.3 doesn't allow that the "set not null" column constraint > be applied in an "alter" statement and the "add primary key" can only be > applied to columns which are designated as "not null." a neat and > frustrating shutout. > > I suppose I could dump the database and reconstruct the schema > correctly, but I'd then have to seriously modify the redhat bugzilla > setup code. moral of this story? the bleeding edge is not for whimps. > > sand@gizmolab.com > >