-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix DB2 LUW supports boolean data type #966
Conversation
Any news about this? |
Hi @regrog, So sorry for the delay, I am taking a look at this. Please bear with us as we streamline our internal processes. -Ronak |
Tagging as RiskLow because:
|
@regrog, slating this for the next sprint and targeting release before end of Q2. Thanks for your patience! |
➤ Erzsebet Carmean commented: Can Community Engagement please clarify if this ticket is correctly labeled as RiskMedium? I see a comment that it is RiskLow but the actual categorization is different. If the ticket is correctly risked as Medium, would this fall to Low if a unit test is added? |
Hi Erzsabet, my vote is yes that would turn this into a Risk Low. |
➤ Erzsebet Carmean commented: I've added test time for one hour to go over tests and do a desk check with development. Thanks for clarifying, Ronak. |
Any plan to merge this? |
In my last PR #865 I forgot a line of code to activate the boolean support.
Test Requirements
┆Issue is synchronized with this Jira Bug by Unito
┆fixVersions: Community 4.3.0,Liquibase 4.3.0