Skip site navigation (1) Skip section navigation (2)

Re: Fw: Talking with other Dbases.

From: Adam Haberlach <adam(at)newsnipple(dot)com>
To: Daryl Chance <dchance(at)valuedata(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Fw: Talking with other Dbases.
Date: 2000-09-28 17:40:51
Message-ID: 20000928104051.A6810@ricochet.net (view raw or flat)
Thread:
Lists: pgsql-general
On Thu, Sep 28, 2000 at 11:00:20AM -0500, Daryl Chance wrote:
> > without knowing the hardware organization & availability of software,
> > it's seems strange that you're considering different database systems
> > for things that one is perfectly capable of performing.  it's a bit of a
> > fallacy that MySQL is better for read only database sites.  on the low
> > end (fewer connections), MySQL might be faster, but you'd have trouble
> > buying hardware that was slow enough that you'd notice the difference. 
> > i've never used MySQL on a heavily loaded web site, but i've heard
> > enough about MySQL breaking down to be a bit concerned about that.  all
> > in all, i'm just not clear on why you're interested in the added
> > headache of multiple database systems & copying data between them.
> 
> As I said in my first email, it just depends :).  I do plan on doing
> tests against MySQL and Postgrest to see which would be better for
> just serving out dynamic content (read only).  Whichever one wins
> out will be the one i'm going to use.  Personally, I've had no problems
> at all with MySQL...I'm looking into postgres because MySQL won't
> do the things I need to do on my next product version.  And, the
> data won't be copied between the 2, MySQL will be dumped to, and thats
> it. So there won't really be much headache on that part.  When the time
> comes, I'll choose.  Currently, I'm just planning ahead.

	We actually have a split shop here, because I set up the bug database
in postgres, and we later hired a web guy who was more familiar with MySQL.
He has since seen the light and converted much of his stuff to use Postgres,
but there are some semi-remote machines using MySQL.  With PHP, even though
there is almost no consistency between database interfaces, it isn't too
hard to use both systems.

	I still reccommend going with one database solution, though.  Much
easier to set up, maintain, etc.  I don't trust MySQL, so I'll let
you guess which one I reccommend...

-- 
Adam Haberlach            | A billion hours ago, human life appeared on
adam(at)newsnipple(dot)com       | earth.  A billion minutes ago, Christianity
http://www.newsnipple.com | emerged.  A billion Coca-Colas ago was
'88 EX500                 | yesterday morning. -1996 Coca-Cola Ann. Rpt.

In response to

pgsql-general by date

Next:From: Adam LangDate: 2000-09-28 18:09:55
Subject: Re: Command names
Previous:From: Travis BauerDate: 2000-09-28 16:28:01
Subject: Re: Command names

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group