Polish "Auto-detect jOOQ dialect"
Closes gh-9355
This commit is contained in:
@@ -3213,23 +3213,17 @@ You can then use the `DSLContext` to construct your queries:
|
||||
|
||||
|
||||
|
||||
==== jOOQ SQL dialect
|
||||
Spring Boot determines the SQL dialect to use for your datasource unless the
|
||||
`spring.jooq.sql-dialect` property has been configured. If the dialect couldn't be
|
||||
detected, `DEFAULT` is used.
|
||||
|
||||
NOTE: Spring Boot can only auto-configure dialects supported by the open source version of
|
||||
jOOQ.
|
||||
|
||||
|
||||
|
||||
==== Customizing jOOQ
|
||||
|
||||
Spring Boot tries to determine the best SQL dialect for your datasource, but you can customize
|
||||
the dialect used by jOOQ by setting `spring.jooq.sql-dialect` in your `application.properties`.
|
||||
Spring Boot uses `SQLDialect.DEFAULT` if it cannot determine the type of your database.
|
||||
|
||||
Spring Boot can only auto-configure dialects supported by the open source version of jOOQ. Dialects
|
||||
supported by the commercial edition only have to be configured manually. For example, to specify
|
||||
Oracle you would add:
|
||||
|
||||
[source,properties,indent=0]
|
||||
----
|
||||
spring.jooq.sql-dialect=ORACLE12C
|
||||
----
|
||||
|
||||
Refer to `org.jooq.SQLDialect` for all valid dialects.
|
||||
|
||||
More advanced customizations can be achieved by defining your own `@Bean` definitions
|
||||
which will be used when the jOOQ `Configuration` is created. You can define beans for
|
||||
the following jOOQ Types:
|
||||
|
||||
Reference in New Issue
Block a user