Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
It looks like we still have a bunch of tables around that are no longer relevant as of the D7 upgrade. For example:
- cvs_files/cvs_files_attic #1302028: Drop legacy CVS integration tables from the DB
- d6_upgrade_filter (this too)
- profile_field/value (migration is complete - dropping one-by one, uninstall profile module when done)
- project_releases (latest data in table from Drupal 4.7)
- project_release_nodes (latest data from Oct. 2013)
- files should be file_(un)managed now, but for some reason patches are still going in there?
- content_type_*
- simplenews_*
- tracker2_node
- tracker2_user
- forum2_index
- comment_alter_taxonomy
- mv_drupalorg_node_by_term
- mv_drupalorg_node_by_vocabulary
- etc.
Most of this stuff is now in field_data_foo_bar tables, but this is non-obvious when you're inspecting the schema and trying to figure out where to query. It also makes the database much larger than it needs to be, which could help pack more dev sites onto a box if it were to be stripped down.
Comments
Comment #1
isntall CreditAttribution: isntall commentedI vote for this as well.
Comment #2
YesCT CreditAttribution: YesCT commentedrelates to #2146967: [Meta] Drupal.org Development Environments also.
Comment #3
drummComment #4
drummComment #5
drummComment #6
drummhttp://cgit.drupalcode.org/infrastructure/commit/?id=0d5a2eb3ad31aa877fe... drops these tables in staging & dev to maybe catch any issues.
Comment #7
drummhttps://docs.google.com/spreadsheets/d/1xZY7qLb_HYgPauOmTQMdSFyRCPjDuNWX... is also an audit Mixologic has been working on.