[Improvement-18249][DAO] Route DataSourceMapper and DataSourceUserMapper access through repository Dao#18259
Open
ruanwenjun wants to merge 1 commit into
Open
Conversation
…per access through repository Dao
Introduce DataSourceDao and DataSourceUserDao so the api layer depends
only on the repository abstraction. The two mappers are bundled because
DataSourceServiceImpl and UsersServiceImpl share both.
DataSourceDao renames mapper.selectPaging / selectPagingByIds to
queryDataSourcePaging / queryDataSourcePagingByIds and folds the
selectByMap("user_id", X) idiom from DataSourceServiceImpl into
queryByUserId(int) so the QueryWrapper-style call no longer leaks
into the api layer.
DataSourceUserDao exposes deleteByUserId / deleteByDatasourceId as void
(the mapper-returned row count was never consulted at the call sites).
Tracking issue: apache#18249
|
This file contains hidden or 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
1 participant
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.
Was this PR generated or assisted by AI?
YES, gpt 5.5
Purpose of the pull request
Introduce DataSourceDao and DataSourceUserDao so the api layer depends only on the repository abstraction. The two mappers are bundled because DataSourceServiceImpl and UsersServiceImpl share both.
DataSourceDao renames mapper.selectPaging / selectPagingByIds to queryDataSourcePaging / queryDataSourcePagingByIds and folds the selectByMap("user_id", X) idiom from DataSourceServiceImpl into queryByUserId(int) so the QueryWrapper-style call no longer leaks into the api layer.
DataSourceUserDao exposes deleteByUserId / deleteByDatasourceId as void (the mapper-returned row count was never consulted at the call sites).
Tracking issue: #18249
Brief change log
Verify this pull request
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:
(or)
Pull Request Notice
Pull Request Notice
If your pull request contains incompatible change, you should also add it to
docs/docs/en/guide/upgrade/incompatible.md