BAH-3525 | Add. Configuration Property To Handle Zero date prohibited Error #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA -> BAH-3525
This PR addresses the "Zero date value prohibited" error configuring OMRS_DB_EXTRA_ARGS to include `&zeroDateTimeBehavior=convertToNull.
During openmrs runtime, OMRS_DB_EXTRA_ARGS sets zeroDateTimeBehavior=convertToNull in JdbcUrl. Upon boot up, openmrs utilizes its own startup script to define the jdbc url. OMRS_DB_EXTRA_ARGS appends any provided parameters to the end of the url.
By default, the connector throws an exception when encountering zero date values, as it aligns with JDBC and SQL standards. This behavior can be adjusted using the zeroDateTimeBehavior configuration property.