From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
Cc: | John DeSoi <desoi(at)pgedit(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: drupal.org MySQL database issues |
Date: | 2007-05-16 16:51:20 |
Message-ID: | 464B3688.3060805@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Jim C. Nasby wrote:
> On Wed, May 16, 2007 at 09:42:36AM -0700, Joshua D. Drake wrote:
>>>>
>>>> I don't know that they would be happy unless they had someone with Pg
>>>> experience helping them.
>>> Is it the drupal code itself that's the issue or just a matter of tuning
>>> PostgreSQL?
>> Both. Obviously tuning postgresql is a big part but they have some odd
>> query issues to deal with. And if they have *any* custom modules, oh boy.
>
> Well, while they're in pain it sounds like a good time to get them
> thinking about changing preferred databases as well as cleaning up some
> of the code... I'm sure that if their preferred database was PostgreSQL
> you'd be seeing more work. :)
Drupal 6 is dropping support for MySQl 3.x and going to a more
normalized data structure. Partly because of me, partly because of a lot
of others. I have spoken with Dries about it personally (via email) and
he is very happy with the idea of moving to a more sane structure overall.
However, there would be a *ton* of work to be done to get them to prefer
PostgreSQL.
Joshua D. Drake
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-05-16 16:53:26 | Re: drupal.org MySQL database issues |
Previous Message | Jim C. Nasby | 2007-05-16 16:44:25 | Re: drupal.org MySQL database issues |