I'm getting "table batch_N has no column named batch_batch" where N is a number that increments each time I try running update.php. This is certainly undesirable behavior. I'm not sure if this is sqlite-specific, but I can't find any related issues for other database systems. This may be two issues:
(1) A malformed sqlite query in update 7055
(2) Errors during the batch process may leave new tables created then abandoned in the database.
Can someone confirm any of this?
Comments
Comment #1
damien tournoud commentedWe don't support HEAD 2 HEAD updates until the first beta version. SQLite is new to Drupal 7, so this update is not supposed to ever run on SQLite.