tangchunbo opened a new pull request #7875:
URL: https://github.com/apache/dolphinscheduler/pull/7875


   …e error in PG database
   
   [FIX-7732][fix] fix column 'is_directory' of table t_ds_resources type error 
in PG database
   
   1. add Boolean2IntTypeHandler both in class Resource.java and 
ResourceMapper.xml
   2. specify typeHandler packages in class SpringConnectionFactory
   3. format class Resource
   4. update `mybatis-plus` version from `3.2.0` to `3.4.0`. The current 
version won’t pass maven test of this 
[MYBATIS-BUG](https://github.com/baomidou/mybatis-plus/issues/2550). Besides 
update the config of `SpringConnectionFactory`
   5. due to 'isDirector' is primitive type, so the test won't cover the 
wrapper type' null situation.
   
   This closes #7732
   
   <!--Thanks very much for contributing to Apache DolphinScheduler. Please 
review 
https://dolphinscheduler.apache.org/en-us/community/development/pull-request.html
 before opening a pull request.-->
   
   
   ## Purpose of the pull request
   
   <!--(For example: This pull request adds checkstyle plugin).-->
   
   ## Brief change log
   
   <!--*(for example:)*
     - *Add maven-checkstyle-plugin to root pom.xml*
   -->
   ## Verify this pull request
   
   <!--*(Please pick either of the following options)*-->
   
   This pull request is code cleanup without any test coverage.
   
   *(or)*
   
   This pull request is already covered by existing tests, such as *(please 
describe tests)*.
   
   (or)
   
   This change added tests and can be verified as follows:
   
   <!--*(example:)*
     - *Added dolphinscheduler-dao tests for end-to-end.*
     - *Added CronUtilsTest to verify the change.*
     - *Manually verified the change by testing locally.* -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to