[wp-hackers] PostgreSQL port status?
computerguru at neosmart.net
Fri Sep 28 08:29:51 GMT 2007
It was too much work to keep it working after every update from the official WP repo, it kept breaking big-time.
If anyone is interested in a PGSQL "port", we discussed this several on here and came to the conclusion that the most viable thing is a plugin that intercepts any calls to the database and uses some regex/mapping voodoo to convert MySQL commands to PostgreSQL commands.
There was a plugin that did that for WP 1.x and it worked just fine..
BTW, am I the only one that has issues with WP calling the ANCIENT, dead, VULNERABLE, and discontinued wordpress-pg.sourceforge.net an "excellent" WordPress port to the PGSQL platform?
I find that misleading. If the intention is to make it look like WP has PGSQL support... well, it doesn't and that line should be removed... Even the link to the pg port seeing as it is only version 1.2.1 WITH the security vulnrerabilities..... and hasn't been updated for years.
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Stephane Daury
> Sent: Friday, September 28, 2007 6:29 AM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] PostgreSQL port status?
> Last I heard was:
> On Sep 04, 2007, at 12:59, Computer Guru wrote:
> > The Postgres Port was mostly working (couple of bugs), but well... it
> > died off, too.
> On Sep 03, 2007, at 22:09, Matt Mullenweg wrote:
> > Q: Why does WordPress only support MySQL? What about DB abstraction?
> > While in theory supporting more databases is better than supporting
> > one, in practice we've found focusing on MySQL has a number of
> > benefits.
> > First, introducing support for databases other than MySQL would
> > increase the testing load for all development quite a bit, as
> > already the combinations of PHP versions, web servers like Apache,
> > Lighttpd, and IIS, and Windows vs Linux cause a number of issues,
> > multiplying that by an arbitrary number of database platforms is
> > daunting.
> > Early on in WordPress' history when DB abstraction was seriously
> > considered we noticed packages like AdoDB were bigger than
> > WordPress itself, which seemed like a lot of weight for little gain.
> > DB independence also requires far more than just dropping in a DB
> > abstraction class, as basic assumptions WP makes about things like
> > primary keys, indicies, auto incrementing fields, LIMITs, and more
> > vary more from DB to DB than a class could support without serious
> > code changes.
> > Finally, MySQL is ubiquitous and has shown to be fast enough and
> > scalable enough for the highest traffic loads, so supporting other
> > DBs would not improve the WordPress experience or our popularity
> > much. As a feature request it comes of fairly infrequently.
> > All that said, every query in WordPress goes through a class called
> > wpdb and that class can be replaced with your own by putting a
> > db.php file in wp-content. So far this has been used for mysqli
> > support and an advanced enterprise DB class called HyperDB, but in
> > theory you could use that, and some wicked regular expressions, to
> > add support for a MySQL-like database without any core code
> > modifications.
> On Sep 27, 2007, at 23:02, Anthony Yarusso wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > I remember a little while ago there was some talk about a PostgreSQL
> > version of Wordpress. How is that coming along, and is there a web
> > site or separate mailing list where I could follow it more closely?
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> > iD8DBQFG/G7IKlAIzV4ebxoRAsYKAJ4xZ80TCiWOpiiCyPG751Yiy4BlrwCfX3Eq
> > RY0nwESPKLeTj8HEhlSJL94=
> > =Wk2a
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers