<h1>Database migration</h1>
<h2 id="mobile">Mobile</h2>
<p>macOS / iOS:</p>
<ul>
<li>Use ObjectMapper cua CoreData de migrate: <a href="https://williamboles.me/step-by-step-core-data-migration/">https://williamboles.me/step-by-step-core-data-migration/</a></li>
</ul>
<p>Android</p>
<ul>
<li><a href="https://medium.com/flutter-community/migrating-a-mobile-database-in-flutter-sqlite-44ac618e4897">https://medium.com/flutter-community/migrating-a-mobile-database-in-flutter-sqlite-44ac618e4897</a></li>
</ul>
<h2 id="backend">Backend</h2>
<ul>
<li>Su dung migration tool tuy ngon ngu
<ul>
<li>Go: sql-migrate</li>
<li>Elixir: ecto</li>
</ul>
</li>
</ul>
<h2 id="tips-best-practices-checklist">Tips / best practices checklist</h2>
<ul>
<li>Luon viet migrate up / down</li>
<li>back up before migration</li>
<li>data validation &#x26; repair</li>
<li>Prefer ORM migration tool</li>
<li><code>Do not</code> deploy the code first: Do not deploy the code first that write to new columns, and then run the migration. It will only result in errors as the code might try to access non-existing column(s).</li>
<li>Ensure the new changes work before you drop anything</li>
<li>Use <code>Feature Flags</code> whenever possible</li>
</ul>

Properties

Location

Stats

Database migration

Mobile

Backend

Tips / best practices checklist

Properties

Stats

Subscribe to Dwarves Memo