On Mon, Mar 21, 2005 at 08:46:17AM +0100, Kurt Roeckx wrote:

On Mon, Mar 21, 2005 at 12:45:37PM +0800, Christopher Kings-Lynne wrote:

...

(Please CC me on responses as I'm not subscribed...)

Hi,

Just wondering if anyone else is working on the PostgreSQL port? I plan to finish it off (hopefully), but I don't want to tread on anyone's toes.

It looks like the PostgreSQL schema files are out of sync with the main MySQL ones, so I supposed no-one's working on it?

I'm working on it. See my current patch in bugzilla. It still needs some work.

To clarify a little.

I've been trying to get the installer working. It currently "works for me", but needs some clean up. This also required me to make the needed schema changes, you can find them in the patch.

There are various other problems that needs to be taken care off. One of the annoying things is that for instance they store a timestamp in mysql in a special format. It looks like this:

page_touched char(14) binary NOT NULL default '', Or: wl_notificationtimestamp varchar(14) binary NOT NULL default '0',

While the pgsql versions currently look like: page_touched timestamp without time zone DEFAULT '1900-01-01 00:00:00'::timestamp without time zone NOT NULL, wl_notificationtimestamp timestamp without time zone DEFAULT '1900-01-01 00:00:00'::timestamp without time zone NOT NULL,

For the wl_notificationtimestamp there is then code that either wants to place a 0 in it, or check that there is a 0 in it, or some other weird thing. There are probably various other things like this.

I really dislike the NOT NULL constraints with a default value on such fields. I would either like to drop the default, drop the NOT NULL constraint (and default), or change the schema in such a way that they are not needed. In case of the watchlist this should be rather easy. We could just drop the default and delete the record instead of setting it to some state that doesn't make sense.

It would be nice of someone could go over all such things.

Kurt