Re: BugTracker (Was: Re: 8.2 features status)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <gsstark(at)mit(dot)edu>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Kenneth Marshall <ktm(at)is(dot)rice(dot)edu>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: BugTracker (Was: Re: 8.2 features status)
Date: 2006-08-19 22:41:49
Message-ID: 44E793AD.2080201@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I wrote:
>
>
> I will check about Greg's complaint about race conditions in updating
> comments. My initial impression is that this is no longer so, but I
> will get a definite answer.
>
>

My impression was correct. Each comment on a bug gets its own row,
marked by bug-id, commenter-id and timestamp.

BTW, there are undoubtedly some infelicities in the schema, but it's not
too bad, and the way the bugzilla code works there is no danger of one
underlying DB platform getting out of synch, as they are all generated
from a single abstract schema.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-08-19 22:57:31 Re: DROP OWNED BY doesn't work
Previous Message Tom Lane 2006-08-19 22:13:42 DROP OWNED BY doesn't work