<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 5, 2014, at 11:34 AM, Rahul Amaram <<a href="mailto:amaramrahul@users.sourceforge.net">amaramrahul@users.sourceforge.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">How do we perform database schema upgrade? Currently I am doing it manually by calling each of the upgrade_from_<from>_to_<to>.sql version files. Does calendarserver_upgrade take care of it? If not, is there an easier way of doing it?</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote><div><br></div><div>Yes, calendarserver_upgrade has one job: to apply any necessary schema and data version upgrades. It is intended to be used immediately after upgrading to a newer version, before the service is started.</div><br><blockquote type="cite">Currently for upgrading from 3.2 files to 5.1 db backend, I am just creating a new db. And the migration from 3.2 files backend to 5.1 db seems to work fine. Is there anything else that I should take care?</blockquote></div><br><div>That sounds like a workable strategy for this upgrade delta. Going forward, calendarserver_upgrade should be all that is needed.</div><div><br></div><div>-dre</div></body></html>