Hi Brian,

Thanks for reporting this, I confirm it is a bug, it appears to be limited to users of MySQL and SQLite.
The correct field name already exists in the db, the error is in the sql statement in code. I have fixed this and committed to svn and will try to get an incremental release out soon with this fix.

I should note that the password does in fact get changed, updating the timestamp of the change occurs after that and this is where the error happens, so the error can be safely ignored until the the fix is released.

Thanks again for letting me know.

Joe