From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-advocacy(at)postgresql(dot)org |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: Feedback from LinuxWorld, London |
Date: | 2005-10-10 22:07:26 |
Message-ID: | 200510101507.27059.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Folks,
> > And of course they are right. Porting from MySQL to PostgreSQL is a
> > problem, one which could only be solved by dumbing down PostgreSQL to
> > accept many of MySQL's idiosyncracies, which isn't going to happen.
>
> It does make me think that we should try to adopt some more of MySQL's
> idiosyntactics even if we don't fully adopt their idiosyncracies.
I really don't agree that the chief problem with porting from MySQL is our
failure to implement ISNULL() or ENUM. I don't even think that's in the
top 10.
The biggest issues are:
1, 2, 3, and 4) Lack of information, e.g. no "PostgreSQL for MySQL users"
handbook.
5) Flakyness of data migration tools, which are largely unmaintained these
days;
6) Lack of data abstraction in many OSS apps (this we can't fix).
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-10-10 22:56:38 | Re: Feedback from LinuxWorld, London |
Previous Message | Josh Berkus | 2005-10-10 21:56:58 | Re: Feedback from LinuxWorld, London |