Say we want to add another column to the crawls table--some new metadata item. Under the existing architecture, I'm not quite sure what would happen if we simply change the create_table_crawls.sql file and re-provision. Ideally, we'd be able to make changes that don't break database logic (e.g., removing the fk column from frontpage_examples, which rows in hs_history use to tie themselves to particular crawler runs) w/o the need either for manual intervention or the fear of data loss.
Say we want to add another column to the crawls table--some new metadata item. Under the existing architecture, I'm not quite sure what would happen if we simply change the
create_table_crawls.sqlfile and re-provision. Ideally, we'd be able to make changes that don't break database logic (e.g., removing the fk column fromfrontpage_examples, which rows inhs_historyuse to tie themselves to particular crawler runs) w/o the need either for manual intervention or the fear of data loss.