From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-advocacy(at)postgresql(dot)org, 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 23:27:15 |
Message-ID: | 20051010232715.GD39569@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Mon, Oct 10, 2005 at 03:07:26PM -0700, Josh Berkus wrote:
> 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).
Well, 1-4 and 6 are all tied together: lack of information (and in some
cases exposure to that info).
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | elein | 2005-10-11 00:05:46 | Re: Feedback from LinuxWorld, London |
Previous Message | Jim C. Nasby | 2005-10-10 23:25:38 | Re: Feedback from LinuxWorld, London |