<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Refactoring on Architecture and Data Blog</title>
    <link>https://sadalage.com/tags/refactoring/</link>
    <description>Recent content in Refactoring on Architecture and Data Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 29 Jun 2007 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sadalage.com/tags/refactoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Long Running Data Migrations during Database Refactorings</title>
      <link>https://sadalage.com/post/long_running_data_migrations/</link>
      <pubDate>Fri, 29 Jun 2007 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/long_running_data_migrations/</guid>
      <description>&lt;p&gt;When you are refactoring large databases, you will have certain tables that have millions of rows, so lets say we are doing the &lt;a href=&#34;http://databaserefactoring.com/MoveColumn.html&#34;&gt;Move Column&lt;/a&gt; refactoring, moving the TaxAmount column from Charge table which has millions of rows to TaxCharge table. Create the TaxAmount column in the TaxCharge table. Then have to move the data from the TaxAmount column in the Charge table to the TaxAmount column you created in the TaxCharge table.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Implementing Make Column Non Nullable</title>
      <link>https://sadalage.com/post/implementing_make_column_non_nullable/</link>
      <pubDate>Fri, 15 Dec 2006 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/implementing_make_column_non_nullable/</guid>
      <description>&lt;p&gt;While working on a Legacy Application with Legacy Database design as part of fixing a bug, I thought this bug would not have ever happened if a particular column was defined as &lt;strong&gt;Non Nullable&lt;/strong&gt; since this particular column was the identifier to the parent table.&lt;/p&gt;&#xA;&lt;p&gt;We had a Customer table and the all the names a customer could have like LegalName, LongName, ShortName etc are stored in the CustomerName table. CustomerName cannot exist without Customer hence its logical that the CustomerName.CustomerID column cannot be nullable and should also have a Foreign Key constraint enforcing the relationship. Implementing just the Foreign Key constraint is not enough since the application could potentially be inserting null values in the CustomerName.CustomerID creating orphan records.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The day I received my Boo</title>
      <link>https://sadalage.com/post/database_refactoring_book/</link>
      <pubDate>Sun, 26 Mar 2006 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/database_refactoring_book/</guid>
      <description>&lt;p&gt;This last week I received my copies of the &lt;a href=&#34;http://www.databaserefactoring.com&#34;&gt;book&lt;/a&gt;, for the first time I could touch what I had worked on for almost a year and half now, I could see it flip the pages. When I opened the UPS box and saw the book for the first time it felt great but in a minute or two I was not feeling anything, after some tea and some walking around I took the book in my hands and started flipping the pages this is when the real feeling started to sink in, but still I was not sure of the situation, was not really sure if it was real, after about 2-3 hours when I saw the book and held the book and started reading, I was started feeling the joy the happiness and all the goodness. I think when I see it being read by others then I will feel a lot different, the other day I saw Nick take out the book out of his backpack I was thrilled to see it being read.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
