From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: [OT] MySQL is bad, but THIS bad? |
Date: | 2006-05-19 00:35:02 |
Message-ID: | 200605182035.02755.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Thursday 18 May 2006 12:38, Josh Berkus wrote:
> Personally, I'd go after MSSQL before I bothered with MySQL. Sure, let's
> make *migration* easier for those who wake up and smell the BS, but
> migration can (and probably should) be one-way.
>
If you want to get users to swtich to your software from your competitors, you
have to eliminate barriers, and a big one for any database is getting locked
into a specific one. People aren't going to take the time to try switching
to postgresql if they can't easily make it back to thier former database.
It's one of the reasons why PostgreSQL's standards compliance is so
important; if you want to swtich to a new database, your best bet is to give
PostgreSQL a shot, because even if you don't like it, we're not going to try
and trap you into our software with bunches of non-standard knobs. Low
barrier to exit == low barrier to entry.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2006-05-19 01:33:16 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | Robert Treat | 2006-05-19 00:14:59 | Re: [OT] MySQL is bad, but THIS bad? |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Seltenreich | 2006-05-19 00:36:24 | Re: PL/pgSQL 'i = i + 1' Syntax |
Previous Message | Mark Dilger | 2006-05-19 00:23:03 | Re: PL/pgSQL 'i = i + 1' Syntax |