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.
Sometimes you have to break abstraction for whatever reason and get to underlying SQL connection. With standard SQL adapter you can get database connection using
Adapter
method inrel.Repository
.But if your SQL adapter is wrapped into
primaryreplica
it becomes impossible to access underlying connection.As a suggestion, in this PR I've exported
WriteAdapter()
method which allows to get access to primary adapter (connection).It's a little bit cumbersome
But it allows to implement a workaround or execute very exotic query otherwise not supported by Repository API.
It probably would make sense to open up
ReadAdapter()
too, but I wanted to keep changes to a minimum.As a context, in my case I'm trying to make aggregation by a float (decimal) field which is not supported by Repository yet.