Conversation

Notices

Embed this notice
Steve Scotten (splicer@makersocial.online)'s status on Friday, 13-Jan-2023 10:07:12 JST Steve Scotten

Anyone have suggestions for workflow developing a site with a database-driven CMS? (#Wordpress but I’ve wrestled with the same question regarding #Drupal and other systems.) #Git seems necessary but insufficient because rolling back code after schema changes have been made can mess stuff up. There are a lot of references online but few address this question and I haven’t yet seen one that addresses it well. I’ve been doing this 28 years now and workflow still perplexes me.

In conversation Friday, 13-Jan-2023 10:07:12 JST from makersocial.online permalink
- Embed this notice
  Evan Prodromou (evan@prodromou.pub)'s status on Friday, 13-Jan-2023 10:07:00 JST Evan Prodromou
  in reply to
  
  @splicer https://en.wikipedia.org/wiki/Schema_migration?wprov=sfla1
  In conversation Friday, 13-Jan-2023 10:07:00 JST permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: login.wikimedia.org
    
    Schema migration
    
    In software engineering, a schema migration (also database migration, database change management) refers to the management of version-controlled, incremental and reversible changes to relational database schemas. A schema migration is performed on a database whenever it is necessary to update or revert that database's schema to some newer or older version. Migrations are performed programmatically by using a schema migration tool. When invoked with a specified desired schema version, the tool automates the successive application or reversal of an appropriate sequence of schema changes until it is brought to the desired state. Most schema migration tools aim to minimize the impact of schema changes on any existing data in the database. Despite this, preservation of data in general is not guaranteed because schema changes such as the deletion of a database column can destroy data (i.e. all values stored under that column for all rows in that table are deleted). Instead, the tools help to preserve the meaning of the data or to reorganize existing data to meet new requirements. Since meaning of the data often cannot be encoded, the configuration...
- Embed this notice
  Evan Prodromou (evan@prodromou.pub)'s status on Friday, 13-Jan-2023 11:47:32 JST Evan Prodromou
  in reply to
  
  @splicer so, look into a schema migration tool and try it.
  
  In conversation Friday, 13-Jan-2023 11:47:32 JST permalink
- Embed this notice
  Steve Scotten (splicer@makersocial.online)'s status on Friday, 13-Jan-2023 11:47:33 JST Steve Scotten
  in reply to
  - Evan Prodromou
  @evan Thank you! I should have written "rolling back code after any change has been made to or in the database", not just schema changes.
  Just thinking out loud here: maybe I should make a dump of the entire database and let that sit in a directory above docroot, and just check that into git. I mean, it's code. Minimal changes mean minimal storage requirements.
  I'm starting to get the sense that there's a reason why large projects hire people that are smarter than me.
  
  In conversation Friday, 13-Jan-2023 11:47:33 JST permalink

Public

Conversation

Notices

Feeds