Yes ! I’ve just released PG4WP 1.1.0, and it is the official release having support for WordPress 2.9.x series
Many thanks to all of you who tested the development releases and gave me feedback and patches to make PG4WP better.
There are still some annoying problems (read more here), but they are in the TODO list for the next release.
Here are some of my ideas for the future :
- resolve most problems introduced by rewriting rules
- build up some kind of “modularized” support for WordPress’ plugins that need special handling
- have WordPress’ import feature work correctly at least with WXR files when using PG4WP
- convert PG4WP into some kind of Framework to easily integrate support for other databases (maybe I’ll call this DBs4WP ?)
- maybe build up a SQLite version, but are there people interested ?
It is time for you to give me any other ideas or wishes, just comment on this post
English
is it possible to run your script with Wordpress MU, so accounts get created as well?
Well this is a good question, and I must admit that I never thought about Wordpress MU when I worked on PG4WP until now.
I don’t know much about the internals in Wordpress MU, but I think PG4WP may work with it.
If you try it, I’d love to get feedback about this (even if it doesn’t work, I think there would be little work to have it working).
On Postgre 8.4.2 I have this error:
Error running :
SELECT DISTINCT MONTH(post_date) AS month, YEAR(post_date) AS year
FROM wp_posts
WHERE post_date > ‘2010-02-01′
AND MONTH( post_date ) != MONTH( ‘2010-02-01′ )
AND post_type = ‘post’ AND post_status = ‘publish’
ORDER BY post_date ASC
LIMIT 1
—- converted to —-
SELECT DISTINCT EXTRACT(MONTH FROM post_date) AS month, EXTRACT(YEAR FROM post_date) AS year
FROM wp_posts
WHERE post_date > ‘2010-02-01′
AND EXTRACT(MONTH FROM post_date ) != EXTRACT(MONTH FROM ‘2010-02-01′ )
AND post_type = ‘post’ AND post_status = ‘publish’
ORDER BY post_date ASC
LIMIT 1
—-
ERROR: function pg_catalog.date_part(unknown, unknown) is not unique at character 184
HINT: Could not choose a best candidate function. You might need to add explicit type casts.
———————
I couldn’t reproduce this particular error, but I found a place in WordPress’ core where it should happen so I integrated a workaround in the current development version of PG4WP (you can download it here).
Please give it a try and tell me if it solves this error for you.
Just wanted to thank you for your work on this plugin, i needed to port wordpress across to postgres and was expecting to roll my sleeves up and code it myself! you have saved me alot of work
thanks!!