Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-2878

Cannot upgrade from 1.8 to 1.9 with error message "Field 'retired' doesn't have a default value"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Must
    • Resolution: Fixed
    • Affects Version/s: OpenMRS 1.9.0
    • Fix Version/s: 1.9 Beta Sprint
    • Component/s: None
    • Labels:
      None

      Description

      I just tried upgrading a 1.6 database through the standalone, and this changeset does not appear to behave correctly:

      	<changeSet id="20110301-1030b-fix" author="sunbiz">
      		<comment>(Fixed)Change concept_reference_term.retired to BOOLEAN</comment>
      		<ext:modifyColumn tableName="concept_reference_term">
      			<column name="retired" type="BOOLEAN" defaultValueBoolean="false">
      				<constraints nullable="false"/>
      			</column>
      		</ext:modifyColumn>
      	</changeSet>
      

      I inspect the database, and this changeset has run, but the concept_reference_term.retired column has a default value of null.

      As a result the changeset "20110301-1030k" fails later on with "Field 'retired' doesn't have a default value".

      Yves ran into the same error outside of the standalone.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                dkayiwa Daniel Kayiwa
                Reporter:
                darius Darius Jazayeri
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: