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

Cascade="all" property isn't set on the Encounter object in the Visit hibernate mapping file

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Could
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: OpenMRS 1.9.2, Platform 1.10.0
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Medium

      Description

      Is there a reason that the cascade="true" property isn't set on the Encounter object in the Visit hibernate mapping file?

      The net result of this is that only way to associate an Encounter with a Visit is to explicitly set the Visit on the encounter via encounter.setVisit. If you attempt to add an Encounter to a Visit by adding it to the "encounters" set associated with the Visit, it does NOT get persisted.

        Attachments

          Activity

            People

            • Assignee:
              mogoodrich Mark Goodrich
              Reporter:
              mogoodrich Mark Goodrich
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Remaining Estimate - 2 hours
                2h
                Logged:
                Time Spent - Not Specified
                Not Specified