Date: Tue, 27 Apr 2004 12:57:46 -0400
From: Tim Conrad <tim@timconrad.org>
To: "Marc G. Fournier" <scrappy@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [HACKERS] What can we learn from MySQL?
Message-ID: <20040427165746.GA1873@external.timconrad.org>
References: <200404262213.44601.jm@poure.com>
	<200404262041.i3QKfZs28845@candle.pha.pa.us>
	<20040427152753.GA34713@external.timconrad.org>
	<20040427124336.R60328@ganymede.hub.org>
	<20040427161246.GB67934@external.timconrad.org>
	<20040427134215.I60328@ganymede.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040427134215.I60328@ganymede.hub.org>
User-Agent: Mutt/1.4.1i

> > Not entirely true. I've read enough on the lists to see Bruce or
> > others saying 'x feature isn't expected until version y.z'. Heck, to
> > me, something that says 'we're hoping for feature x in version y.z',
> > but it's not an exact science.  See the MySQL releases as an example
> > :)
> 
> Ah, then in that case, look at the TODO list, pull out all items that have
> a name beside them, and for those, they aren't expected until the next
> version .. :)

But the list is loooonng...and my brain is weeeaaaakkk. :)

Seriously, though. I was looking through the list yesterday trying
to figure out something, and it was kind of hard to do.But, more to
my point, this stuff is in the MySQL manual, making it easy to find.
(Yes. I know what MySQL includes kind of blows, but, it's better
than nothing)


Tim