should have googled first!

I’m not sure if you’re using the latest version of this patch - I fixed some bugs as well as changed things for the 1.5.3 patch. Try using the 1.5.2 patches regular files and the 1.5.3 versions db-sqlite.php file. You also might have some problems with sqlite if you’re running php4 with the pecl version of sqlite instead of php5 with the built in version - different features are available with the two.

so if sqlite doesn’t like limit on update or delete (why the heck would you need it anyway…ah nevermind, this is mysql nuttiness) - just match UPDATE(*)LIMIT(*) and clip it off at the limit statement

As far as the header stuff goes, I didn’t touch it, so don’t ask me - take a look at the files I did edit, the only things I messed with were strictly query related, so the header problem is beyond my scope - this site runs the same code and I don’t have any problems

I have also a problem with php function header() when i “Unapprove” a comment in the admin section (Manage > Posts). It’s the classic problem when you call too much header() to set http header.

now if they’d take a look at http://trac.wordpress.org/ticket/1395 maybe I’ll make some noise for mysqli support and sqlite support

Sqlite will most likely come BEFORE any other db, why? because of the very powerful way you can register functions for sqlite right from php - why is this useful? because wordpress is VERY dependent on mysql date functions (which I replicated in php for sqlite), there was a thread on hackers about it…personally I prefer to use the db specific date stuff instead of unix timestamps, it’s more useful and flexible. The point is to write the functionality into your db abstraction layer - in my pff classes I have a function called, well, functions, that you send a generalized function name (date, time, substring) and any arguments for it, and each db driver then writes out the proper function to use

Postgres is a little more strict with their sql syntax, but they also can use udfs to fake mysql functions so if wordpress would clean it’s sql act up a little I could take out the regex stuff in the hack - which does add time onto everything

also, for some odd, strange reason instead of using last_insert_id type stuff there are several places in the wordpress source that use ’show table status’ to get the autoincrement value for a table (stupid)

I have svn installed - tortoisesvn is my favorite thing , I’ll just need to diff every file I changed against the current release - blah

Thanks for the praise - hope you enjoy

I hope they will use your patch in the main wordpress tree. It’s super, you have done a fantastic work

but I’ll be gone for a few weeks here on vacation so gimme some time