Database design updated

I'm gone through and re-thought a lot of the database, and updated it. For some reason, however, my router's giving me problems, so I'm having a problem uploading to CVS (or downloading, for that matter, and I *did* RTFM and there's no misconfiguration that I can see).

Being the only developer on the project, it's looking like about a year of work ahead of me, between doing odd jobs, etc., to keep my head above water.

Anyway... the database is now slightly more efficient and I've decided on InnoDB tables in MySQL in order to allow for transaction processing (the row-locking feature will speed things up considerably for this reason). In general, however, all tables that don't require row-locking will be MyISAM. I'm using 4.1.x MySQL and 5.x PHP with GD2 and some other goodies that will help prevent automated entry based a little on some ideas I saw on the CAPTCHA site. Damaged images may be able to be dropped directly into the database, which means that images residing on the server will not be able to be harvested. Still working on this idea, however, and I don't have it working.