Re: BUG #4999: select 'a' < 'A' is true, but should be false . . . - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .
Date
Msg-id 1251148590.10096.28.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .  (Greg Stark <gsstark@mit.edu>)
Responses Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .  (Greg Stark <gsstark@mit.edu>)
List pgsql-bugs
On mån, 2009-08-24 at 20:10 +0100, Greg Stark wrote:
> It's completely email based so we could just treat it as a mailing
> list without having to go visit a web interface to stay up to date. We
> could add CVS/whatever hooks so whenever a commit message says it
> closes a bug it gets closed automatically.  Effectively it would
> require no operational changes for developers who would just
> participate on a mailing list and commit changes like usual.

Well, all you'd really need is that if you close a bug, you indicate
that say via an email header

X-PG-Bugs-Close: 12345

and then spice up the archives display to show that somehow.  But the
chances of getting people to use that consistently is pretty small.

Some kind of simple request tracker where you just forward all bugs that
you think need saving would also help.  You wouldn't need to copy all
the follow-up there; it would only serve as a pointer into the archives.

In fact, all you need is

CREATE TABLE bugs (
   nr int
);

and an interface to display that and add to that.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .
Next
From: Greg Stark
Date:
Subject: Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .