<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Léo Moro</title>
    <description>The latest articles on DEV Community by Léo Moro (@iinku).</description>
    <link>https://dev.to/iinku</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F138837%2F4505b67a-9d71-49b2-a83b-327a0b522387.png</url>
      <title>DEV Community: Léo Moro</title>
      <link>https://dev.to/iinku</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/iinku"/>
    <language>en</language>
    <item>
      <title>How do you handle database migrations ?</title>
      <dc:creator>Léo Moro</dc:creator>
      <pubDate>Wed, 15 Apr 2020 17:25:54 +0000</pubDate>
      <link>https://dev.to/iinku/how-do-you-handle-database-migrations-1g62</link>
      <guid>https://dev.to/iinku/how-do-you-handle-database-migrations-1g62</guid>
      <description>&lt;p&gt;At work, we use flyway to manage our database migrations. We have multiple test environnement and multiple staging version of our applications. Every Sunday, a script download and install a fresh database backup from the prod. How do you handle your migrations in this scenario ? Every time you install a new version, you downgrade to the prod version ? &lt;/p&gt;

</description>
      <category>database</category>
      <category>sql</category>
      <category>help</category>
      <category>ask</category>
    </item>
  </channel>
</rss>
