# Is it possible to upgrade a CVS version?

**URL:** <https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759>\
**Category:** Management and Administration\
**Created:** [December 11, 2009, 11:01am UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759 "2009-12-11T11:01:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 11, 2009, 11:01am UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/1 "2009-12-11T11:01:14Z")

</div>

**[tsoukase](https://sourceforge.net/u/tsoukase/)** wrote on [Friday, December 11, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#9a31):

I want to follow the upgrade chain in the long-term. Can I upgrade any CVS version to a new one or even to the next stable one? Or the only “upgradable” versions are the stable ones that lead to the next stable as is noted ?

Thanks

&nbsp; : [http://www.openmedsoftware.org/wiki/OpenEMR\_Upgrade\_Guides](http://www.openmedsoftware.org/wiki/OpenEMR_Upgrade_Guides)

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 12, 2009, 5:17pm UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/2 "2009-12-12T17:17:34Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Saturday, December 12, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#3a76):

hey,

The issue is with the sql database. If you check out openemr/sql you will note there are incremental sql database updates from version to version. Since the “incremental” upgrade file is not “finalized” when you upgrade to/from a cvs there is potential to cause problems in the database. Most of the upgrades that have had problems seem to be related to users trying to upgrade from a cvs version. If you can , I’d avoid it, but if you really need a feature, then you’ll need to carefully analyze your mysql database when you upgrade in future to a stable release.

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 12, 2009, 6:05pm UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/3 "2009-12-12T18:05:17Z")

</div>

**[sunsetsystems](https://sourceforge.net/u/sunsetsystems/)** wrote on [Saturday, December 12, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#a5da):

Actually this is less of a problem than it used to be.&nbsp; The sql\_upgrade.php script works together with directives (in the form of comments) in the SQL scripts to check each individual database upgrade step to see if it is already done.&nbsp; If so, then it is skipped.&nbsp; So in theory you should be OK.

Rod&nbsp;  
([http://www.sunsetsystems.com/)](http://www.sunsetsystems.com/%29)

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 12, 2009, 6:13pm UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/4 "2009-12-12T18:13:22Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Saturday, December 12, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#a258):

hey,

But it’s not without risk. For example:

- if we introduce a bug into the database script and then fix(remove it) it, your still stuck with the bug

- if we introduce a new table; then you use this cvs version; then we introduce a new column or fix into that new table; you’d never get that column or fix in the upgrade (since it’s hidden behind a ifNotTable function).

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 12, 2009, 6:25pm UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/5 "2009-12-12T18:25:15Z")

</div>

**[sunsetsystems](https://sourceforge.net/u/sunsetsystems/)** wrote on [Saturday, December 12, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#f192):

Yes of course.&nbsp; Developers can minimize the risk by being careful.&nbsp; For example in your second case, if a day or more has elapsed between creating the new table and adding a new column, then put the column in as a separate step in the upgrade script.

Rod&nbsp;  
([http://www.sunsetsystems.com/)](http://www.sunsetsystems.com/%29)

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [December 14, 2009, 1:38pm UTC](https://community.open-emr.org/t/is-it-possible-to-upgrade-a-cvs-version/1759/6 "2009-12-14T13:38:53Z")

</div>

**[tsoukase](https://sourceforge.net/u/tsoukase/)** wrote on [Monday, December 14, 2009](https://sourceforge.net/p/openemr/discussion/202505/thread/b67a6fca/#4294):

Actually, if the only concern is the structure of the sql-database, the upgrade is always possible if the changes in it are made either manualy or through a script.

Thanks.