public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tim Conrad <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: PostgreSQL advocacy <[email protected]>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: Tue, 27 Apr 2004 12:12:46 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Tue, Apr 27, 2004 at 12:58:59PM -0300, Marc G. Fournier wrote:
> On Tue, 27 Apr 2004, Tim Conrad wrote:
> 
> > 2) There doesn't seem to be a clear roadmap on Postgres features.
> >    When certian things are expected. There's the TODO list that
> >    Bruce maintains, but it only outlines 'near' fixes. MySQL has a
> >    nice listing of what to expect in certian future versions.
> 
> Not possible for us, since we have no "upper management" that dictates
> what features get added, for when ...

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
:)

> 
> >    I know
> >    it's not a perfect list, but it'd be nice to know when full blown
> >    replication will be included in PostgreSQL as an example.
> 
> Never, since there is no such thing as a 'full blown replication', since
> there is no *one* way to do replication ...

It was puretly there for example purposes...
> 
> >  3) There's the issues of 'advanced database features' in general.
> >     Many MySQL applications perform much of their logic in the
> >     application level, instead of the database level. They do this
> >     because there aren't things like triggers or stored procedures
> >     in MySQL. As the saying goes, 'if mohammad won't go to the
> >     mountain, bring the mountian to mohammad'. Why not do some
> >     simple explainations as to why these things are good, and what
> >     they do, and how to use them in real context?
> 
> Just a matter of someone writing and submitting it ... how are your
> writing skills? :)
> 
> >  4) As other peole have noted, there's no windows build readily
> >     available for Postgres. There may be, but it's difficult to
> >     find. If someone's used to running, say, Oracle, and all they
> >     have is a windows machine to test something out on, MySQL has
> >     compiled binaries ready to go.
> 
> there is no native windows currently available, but its being worked on
> for 7.5 ... after which, a pre-compiled binary becomes automatic ...
> 
> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: [email protected]           Yahoo!: yscrappy              ICQ: 7615664

view thread (145+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] What can we learn from MySQL?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox