How can I handle upgrades of the database in later versions gracefully?
<p>So I have my app almost ready to go. I have just been wondering about when I update it how the upgrading of the database will work.</p>

<p>Basically it is a quiz and I will be adding and removing questions and the users personal data needs to be kept for instance. How many correct and incorrect answers and for which questions etc.</p>

<p>This gets a bit more complex when you think I may want to remove or add new questions, and even worse when changing structure.</p>

<p>But do I have to worry about this code now? I am thinking that the second release of my app could contain the update code. This would allow me to release the initial app earlier and worry about the upgrade in the background.</p>

<p>Is this possible? Or must you have the upgrade code as it were <em>on standby</em>?</p>
