[WP-pg-devel] The Return of Progress Report on WordPress-pg 1.5

[William A.C. <wil...@ca...>]

Pardon the formatting here, I'm basically just pasting the blog entry I=20=

just made on the progress since it sums things up pretty well...
I spent some quality time in a local coffee shop this evening pounding=20=

out more work on the port. Without further rambling here is the good=20
and bad side of where we=E2=80=99re at now:
	=E2=80=A2 	Installs from scratch works in my test =
environment
		=E2=97=A6 	 The logo image on the install page =
depends on a remote image,=20
probably should get fixed to be local
		=E2=97=A6 	The table creation statements in step 2 =
interleave wrong in my=20
browser
		=E2=97=A6 	There are some errors thrown by the =
index manipulation code in=20
step 2
		=E2=97=A6 	Haven=E2=80=99t tested an upgrade =
scenario of any sort (this probably=20
won=E2=80=99t work)
		=E2=97=A6 	Haven=E2=80=99t tested an import =
scenario of any sort (this certainly=20
won=E2=80=99t work)
	=E2=80=A2 	Creating new posts works
	=E2=80=A2 	Creating new comments works
		=E2=97=A6 	 Comment status code is probably broken =
(badness related to=20
comment_approved growing a new =E2=80=9DSPAM=E2=80=9D status which =
I=E2=80=99ve wound up=20
implementing using NULL since this was made a boolean in the 1.2.x=20
ports)
	=E2=80=A2 	Creating new categories works
	=E2=80=A2 	Creating new links works
	=E2=80=A2 	The front page as well as individual post pages =
display correctly
	=E2=80=A2 	The admin pages display mostly correct
		=E2=97=A6 	 There is some weirdness with the =
categories list in Manage=20
Categories where root items are displayed twice except for the id 0=20
=E2=80=9DUncategorized=E2=80=9D entries.
	=E2=80=A2 	I=E2=80=99m seeing some database error messages =
on creating a post but=20
can=E2=80=99t determine where they are coming from due to wp-db being =
obtuse=20
and various bits of WordPress code turning error reporting off for no=20
good reason
	=E2=80=A2 	Haven=E2=80=99t even begun to look at xmlrpc.php =
yet. Making that go seems=20
like it is going to be a bit of an adventure

Things accomplished today:
	=E2=80=A2 	Got the posts and categories displaying =
correctly on the end user=20
parts
	=E2=80=A2 	Fixed places where LIMIT M,N needed to become =
LIMIT N OFFSET M for=20
PostgreSQL
	=E2=80=A2 	Fixed more badness where =E2=80=9DSHOW TABLE =
STATUS=E2=80=9D was used to get the=20
auto_increment counter for new categories, which resulted in new=20
category creation working properly.
	=E2=80=A2 	Default post category is now the special =
=E2=80=9DUncategorized=E2=80=9D category.=20
Some weird stuff was happening where the post_category would be 0 but=20
wp_post2cat would have 1 in it for some reason

Things on the todo list:
	=E2=80=A2 	Cleanup database error messages to be able to =
know when things go=20
wrong without tailing PostgreSQL=E2=80=99s logs
	=E2=80=A2 	Make install.php use local images only
	=E2=80=A2 	Fix install.php step 2 to use reindex rather =
than dropping and=20
recreating indexes (which may be necessary for MySQL but not us)
	=E2=80=A2 	Figure out and fix what is throwing the SQL =
syntax errors in=20
post.php on =E2=80=9Dsave as draft=E2=80=9D
	=E2=80=A2 	Fix the Category List order strangeness in =
wp-admin/categories.php
	=E2=80=A2 	Change the default links in the install to not =
include every person=20
who ever wrote a line of WordPress code and instead point to the=20
project pages and useful resources like the WordPress Codex.
	=E2=80=A2 	Change the default hello world comment and text =
to have some =E2=80=9DLorem=20
Ipsum=E2=80=9D copy in them to fill out space better.

So I=E2=80=99m going to be checking this all into CVS in a few minutes. =
I also=20
took the time to add my thoughts about database abstraction approaches=20=

on the "Using Alternative Databases" page over on the WordPress Codex=20
wiki. The WordPress-specific abstraction layer is going to work out=20
best in the long haul. Highly generic abstraction layers for database=20
access generally do poorly from optimization, performance and ease of=20
coding points of view. And as the time spent on the 1.5 port=20
demonstrates, the existing database code is a total fiasco for trying=20
to add new databases to.
--=20
WAC