title: Core Data migration and shipping the database file
body: <p>Currently i have an app shipped to App Store. I want to include the populated database to the next version(i will copy the .sqlite file to the main bundle), but some data will need to be loaded, depending on location. The next version's data model has significant changes. Furthermore, next versions would also have changes to data model. What do i do?</p>
  
  <p>Do i need to care of migration if i ship the DB? If i check whether the DB file exists, and if it's not, copy it from the main bundle - it won't affect current users, but if i won't check - it would get replaced every time user launches an app. It's still unclear to me how to deal with next versions. I assume i need to keep the shipped DB named equally from version to version, but it will cause the data loss on update.  </p>