Re: [pgsql-advocacy] What can we learn from MySQL? - Mailing list pgsql-hackers

From Tim Conrad
Subject Re: [pgsql-advocacy] What can we learn from MySQL?
Date
Msg-id 20040427165746.GA1873@external.timconrad.org
Whole thread Raw
In response to Re: [pgsql-advocacy] What can we learn from MySQL?  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: [pgsql-advocacy] What can we learn from MySQL?  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
> > 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

pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Next
From: Peter Eisentraut
Date:
Subject: Re: PITR Phase 1 - Code Overview (1)