cosmetic doc improvements for jdbc component #2148
Open
Conversation
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
Signed-off-by: Nathan Xu <nathan.qinghyang.xu@gmail.com>
NathanQingyangXu
force-pushed
the
cosmetic-doc-improvements-jdbc
branch
from
e9f297d to
b3e6c63
Compare
spring-projects-issues
added
the
status: waiting-for-triage
NathanQingyangXu
changed the title
NathanQingyangXu
commented
Oct 4, 2025
| + You can let Spring auto-discover your javadoc:org.springframework.data.jdbc.core.dialect.JdbcDialect[] by registering a class that implements `org.springframework.data.jdbc.core.dialect.DialectResolver$JdbcDialectProvider` through `META-INF/spring.factories`. | ||
| Dialects are resolved by javadoc:org.springframework.data.jdbc.core.dialect.DialectResolver[] from a `JdbcOperations` instance, typically by inspecting `Connection.getMetaData()`. + | ||
| You can let Spring auto-discover your javadoc:org.springframework.data.jdbc.core.dialect.JdbcDialect[] by registering a class that implements `org.springframework.data.jdbc.core.dialect.DialectResolver$JdbcDialectProvider` through `META-INF/spring.factories`. | ||
| `DialectResolver` discovers dialect provider implementations from the class path using Spring's `SpringFactoriesLoader`. |
There was a problem hiding this comment.
I assume the intention was to insert a hard line break here. Currently, a literal "+" is displayed in the resulting doc instead.
NathanQingyangXu
commented
Oct 4, 2025
| The query you provide must match the format the `RowMapper` expects. | ||
| Columns for all properties that are used in the constructor of an entity must be provided. | ||
| Columns for properties that get set via setter, wither or field access are optional. | ||
| Columns for properties that get set via setter or field access are optional. |
There was a problem hiding this comment.
I am not sure about the wither, though I am almost sure it is a typo or defect, so I simply deleted it.
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.
Seems the doc has room for improvement. This PR tries to correct some obvious defects and is only restricted to Spring Data JDBC module. Further follow-up PRs might be created in the future.