From: Patrick Macdonald <patrickm@redhat.com>
To: Jonathan Sand <sand@gizmolab.com>
Cc: rhdb@sources.redhat.com
Subject: Re: postgresql 7.3
Date: Thu, 06 Mar 2003 15:22:00 -0000 [thread overview]
Message-ID: <3E6767B2.7030205@redhat.com> (raw)
In-Reply-To: <F6E081A7-4FB0-11D7-BEEB-003065F408F0@gizmolab.com>
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
>
>
next prev parent reply other threads:[~2003-03-06 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 8:53 Jonathan Sand
2003-03-06 15:22 ` Patrick Macdonald [this message]
2003-03-07 9:31 Jonathan Sand
2003-03-07 15:16 ` Patrick Macdonald
2003-03-07 17:56 Jonathan Sand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E6767B2.7030205@redhat.com \
--to=patrickm@redhat.com \
--cc=rhdb@sources.redhat.com \
--cc=sand@gizmolab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).