postgres – why? (why not?)

  • (Im sure there was a dev blog somewhere so here’s hoping Matt et al spots this one)
    I don’t use mySQL it’s that simple. I use postgreSQL. I thought to myself hey come on it can’t be that hard so off I went into the WordPress code.
    The schema is a snap to move over so that’s that bit out of the way and dropping in a slightly modified pgsql file for exsql was a no brainer. Some of the SQL statements I wonder about they’re exact purpose but on the whole it’s been quite easy to do.
    Has anyone one seriously about doing this? The code wouldn’t be that difficult to rewrite to accomodate such a beast. If you rewrite some of your SQL and make your date handling more generic I expect you’d be 90% of the way there.
    I’m currently converting 1.0.2 so yell if you’re interested. I’ll prob retrace my steps and make it fully mySQL/pgSQL compatible as a proof of concept and you can decide what to do with it from there.
    DasFreak

Viewing 3 replies - 1 through 3 (of 3 total)

  • I thouhgt that WordPress used ezSQL? At least that is listed on the developers page. If so, I don’t know why it should be difficult at all, but I don’t know the code in depth.

    I think the issue is that the developers are currenlty using some MySQL-specific query syntax. Supporting PostgreSQL is certainly feasible, but some infrastructure might need to be introduced to support the appropriate queries for the different database engines.

    I sure hope that they do implement support for PostgreSQL. Currently I’m running Movable Type, but with the new licesing I’m screwed. Even more screwed when my Site admin told that he didn’t wat mySQL on his server at all…
    Please please please. pretty please with sugar on top. Make a PostgreSQL version of WordPress.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘postgres – why? (why not?)’ is closed to new replies.