Likewise, the recent commit resolved the issue for me. +1 on getting an updated/fixed release ASAP.
The most likely cause of this issue (and similar ones with other tables) is that your SQL got truncated when being imported. Typically this happens when you're importing your database via PHPMyAdmin or similar software, and the request times out. Sometimes, though, it happens when there's some kind of typo or issue in the SQL file. I've also seen it when there's nothing wrong with the SQL file itself, but for some reason an old table is not being fully dropped in the database before re-importing.
Either way, when an error occurs during import, the remaining SQL statements are not executed. Since the errors are often towards the end of the file, most of the statements are run, resulting in a database that appears to be complete, but which is missing many of the later statements that set default values and incriminators for tables. The lack of those features on the tables is what's resulting in the errors folks are reporting here.
You can try fixing your tables one by one, but it's very difficult. A better option is to:
1) Clear your database completely (i.e. drop all tables) and verify there are no lingering tables.
2) Re-import your SQL file, ideally from the command line to ensure there are no network issues.
3) Watch for any errors during import. If there are errors, you may need to manually remove the offending SQL statements in the import file.
If you can get the SQL to import with no issue (and assuming you've got a complete SQL dump to begin with), your issues should resolve.