I download version 1.0.1 ,but I can’t find any different form 1.0.0
except version number.
The manage comments list function do not work well still.

The plugin does not appear to handle permalinks correctly. Whenever I click on a post I get a error 404 from wordpress itself. This means that permalinks on the server is working fine but something in the database lookup is not working. I tested on the same server with both mysql and sqlite. Mysql works fine but sqlite does not. The website provided in this comment is a test one I have running for public access that uses sqlite. It has permalinks enabled. All other links other than the post ones work.

Hi Justin,

Thanks for responding so quickly.

WordPress 2.5.1
PDO for WordPress 1.0.2 (latest)
I have tested on both Lighttpd and Apache.

When you asked about which permalinks don’t work I went and checked to see which of the standard ones are broken. I found that the Date based ones (“Day and name” and “Month and name”) are broken however the Numeric one works fine. So it looks like it is the date being in there that is fouling it up. I’ll check it some more and see specifically which part(s) is.

Ok. Looked at it further. The year part is ok. It is when it goes to do the day or month number. Don’t ask me why. I’ll go through today checking other structure tags and see if any others are causing an issue.

Last comment for now (I promise). I finished going through the list. They were paired with postname which is already known to be ok. First list are all good and working and the second one causes a 404 error to be generated by wordpress (not the server). With these in mind I just discovered that date based archives do not work since they use either the day or month number in the address.

Good to go!
—————-
year
postname
post_id
category
author

These don’t work.
———————
monthnum
day
hour
minute
second

Ok. I’m going to have to update one more time. I don’t know if permalinks are even the cause here. I just noticed that even if permalinks is off then the dated archives are broken. You can even try them on your own site. The ones for this year produce a not found error (even though we know there should be something there) however the ones for last year work fine. Odd…

Yes. Please do send me a copy to my email address (I think you already have it).

I try to use pdo for wordpress on my gentoobox with no mysql.
I got only white screen.
This is because in wp-include/wp-db.php is include in pdo/db.h and wp-include/wp-db.php need mysql.

You nedd mysql to use sqlite (gasp).

solution in pdo/db.php :
set a value to $wpdb juste after declaring it global

if ( ! isset($wpdb) ){
        global $wpdb;
        $wpdb=1;
        echo "require wp-db.php";
        require_once ABSPATH.'wp-includes/wp-db.php';
        echo "back require wp-db.php";
        unset($wpdb);
}

Hello, just before to take the my car for holydays.
The creation of wordpress (not PDO) call mysql functions, so if you want to run on a pure salite platform you must inhibit it.

in wp-include/wp-db.h tou have

function __construct($dbuser, $dbpassword, $dbname, $dbhost) {
register_shutdown_function(array(&$this, "__destruct"));

$this->dbh = @mysql_connect($dbhost, $dbuser, $dbpassword, true);

and this call to mysql_connect was THE problem

Hello,

I have a strange problem with pdo sqlite the link http://bertrand.belguise.net/blog/?m=200809 doesn’t give me the posts …
The same sructure of blog with mysql don’t give me the same problem. May be a date problem with pdo sqlite.

(WordPress 2.61)

I use the last version font on wordpress.org. (1.0.2)
And the problem is cause by strftime …
strftime return with %m return 2 characters string
so
Select count(*) ….. AND strftime
(‘%m’,post_date)= 09
give me 0
and
Select count(*) ….. AND strftime
(‘%m’,post_date)= ’09′
give me two

Yes of course where can i get it ?

for the moment i have modified pdo_sqlite_driver.php like this

private function _rewrite_datetime_functions($matches){
//may need to expand this to other functions.
switch (strtolower($matches[1])){
case "year":
return " cast( strftime('%Y',{$matches[2]}) as integer ) ";
break;
case "month":
return " cast( strftime('%m',{$matches[2]}) as integer )";
break;
case "day":
case "dayofmonth":
return " cast( strftime('%d',{$matches[2]}) as integer)";
break;
case "unix_timestamp":
return " cast(strftime('%s', {$matches[2]}) as integer)";
break;
}
}


Ok i’ll wait, for the moment my fix (with the cast) solve my problem as you can see my worrd works fine

and i don’t see errors in my database with SqliteManager i have
post_date = ’2008-08-30 18:30:12′
the problem that yoiy patch fix is for the first day of a month and in my database the post_date is right like this
’2008-09-04 21:36:03′ i think that we don’t speak of same problem mine was because ’08′ is not equal to 08 (the string is not equal to the integer.

i can confirm that. BertrandB’s solution is working indeed. the dateupdate-script posted by justin above does not help. with the integer-casts i solved the broken page-archive due to wrong string vs. integer comparison – like bertrandb already said it: ’08′ != 8

thanks bertrand, now i have my page-archive finally working

Works great, thank you