After enabling all core modules in a fresh Drupal 6 (dev) install, then performing an upgrade to Drupal 7 (dev), the following tables are left over and not claimed by any schema.

access  (from user.module)
blogapi_files   (from blogapi.module)
d6_upgrade_filter   (renamed from 'filters' in D7 filter.install)
files  (from system.module)
taxonomy_term_relation   (renamed from 'term_relation' in taxonomy.install)
taxonomy_term_synonym      (renamed from 'term_synonym' in taxonomy.install)

This list should be reviewed, for possible oversights. If the omission is deliberate, messages should be emitted about these tables during the upgrade process.

Comments

lyricnz’s picture

lyricnz commented

Oh yeah, with all the patches I provided recently, there are no longer any schema mismatches after the upgrade! Woop!

#1154812: Poll Schema mismatch after upgrade D6 to D7
#1154822: User Schema mismatch after upgrade D6 to D7
#1154808: Node Schema mismatch after upgrade D6 to D7
#1154820: System Schema mismatch after upgrade D6 to D7
#1154806: Comment Schema mismatch after upgrade D6 to D7
#1154802: Block Schema mismatch after upgrade D6 to D7

catch’s picture

catch
he/him
Primary language English
commented
Issue tags: +D7 upgrade path

access - deliberate
blogapi_files (from blogapi.module) - deliberate
d6_upgrade_filter (renamed from 'filters' in D7 filter.install) - deliberate
files (from system.module) - no idea.
taxonomy_term_relation (renamed from 'term_relation' in taxonomy.install) - deliberate
taxonomy_term_synonym (renamed from 'term_synonym' in taxonomy.install) - deliberate

boran’s picture

boran commented
Status: Active » Closed (won't fix)

Tables are kept around deliberately. We prefer not to drop tables, they need to be cleaned up manually once an upgrade has been successfully completed.