CSV parser should save cached objects once file has been loaded. #277
Labels
Comments
alaboso
pushed a commit
to alaboso/openmrs-module-initializer
that referenced
this issue
Sep 10, 2024
…has been loaded.
alaboso
pushed a commit
to alaboso/openmrs-module-initializer
that referenced
this issue
Sep 13, 2024
…has been loaded.
alaboso
pushed a commit
to alaboso/openmrs-module-initializer
that referenced
this issue
Sep 13, 2024
…has been loaded., - Updating pom xml to include dependency exti18n required by addresshierarchy and stockmanagement required by billing
Ruhanga
pushed a commit
that referenced
this issue
Sep 13, 2024
Ruhanga
pushed a commit
that referenced
this issue
Sep 13, 2024
Ruhanga
pushed a commit
that referenced
this issue
Sep 13, 2024
…d., - Updating pom xml to include dependency exti18n required by addresshierarchy and stockmanagement required by billing
Ruhanga
pushed a commit
that referenced
this issue
Sep 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When objects from a previous loader remain in the current Hibernate session and haven't been fully persisted, there is a risk that subsequent loaders could clear them before they are saved (e.g
DisplaysCsvParser#save()).To address this bug and ensure proper persistence, the CSV parser should persist cached objects after processing each batch of lines.
The text was updated successfully, but these errors were encountered: