类 JimmerProperties
java.lang.Object
org.babyfish.jimmer.spring.cfg.JimmerProperties
-
嵌套类概要
嵌套类 -
构造器概要
构造器构造器说明JimmerProperties(String language, String dialect, boolean showSql, org.babyfish.jimmer.sql.runtime.DatabaseValidationMode databaseValidationMode, JimmerProperties.DatabaseValidation databaseValidation, org.babyfish.jimmer.sql.event.TriggerType triggerType, org.babyfish.jimmer.sql.EnumType.Strategy defaultEnumStrategy, Integer defaultBatchSize, Integer defaultListBatchSize, Integer minOffsetForIdOnlyScanMode, Collection<String> executorContextPrefixes, String microServiceName, JimmerProperties.Client client, Map<String, JimmerProperties.Client> clients) -
方法概要
修饰符和类型方法说明intorg.babyfish.jimmer.sql.EnumType.Strategyintorg.babyfish.jimmer.sql.dialect.DialectIf this option is configured, when jimmer calls back `org.babyfish.jimmer.sql.runtime.Executor.execute` before executing SQL, it will check the stack trace information of the current thread.intFor RDBMS, pagination is slow if `offset` is large, especially for MySQL.org.babyfish.jimmer.sql.event.TriggerTypebooleantoString()
-
构造器详细资料
-
JimmerProperties
public JimmerProperties(@Nullable String language, @Nullable String dialect, boolean showSql, @Deprecated @Nullable org.babyfish.jimmer.sql.runtime.DatabaseValidationMode databaseValidationMode, @Nullable JimmerProperties.DatabaseValidation databaseValidation, @Nullable org.babyfish.jimmer.sql.event.TriggerType triggerType, @Nullable org.babyfish.jimmer.sql.EnumType.Strategy defaultEnumStrategy, @Nullable Integer defaultBatchSize, @Nullable Integer defaultListBatchSize, @Nullable Integer minOffsetForIdOnlyScanMode, @Nullable Collection<String> executorContextPrefixes, @Nullable String microServiceName, @Nullable JimmerProperties.Client client, @Nullable Map<String, JimmerProperties.Client> clients)
-
-
方法详细资料
-
getLanguage
-
getDialect
@NotNull public org.babyfish.jimmer.sql.dialect.Dialect getDialect() -
isShowSql
public boolean isShowSql() -
getDatabaseValidation
-
getTriggerType
@NotNull public org.babyfish.jimmer.sql.event.TriggerType getTriggerType() -
getDefaultEnumStrategy
@NotNull public org.babyfish.jimmer.sql.EnumType.Strategy getDefaultEnumStrategy() -
getDefaultBatchSize
public int getDefaultBatchSize() -
getDefaultListBatchSize
public int getDefaultListBatchSize() -
getMinOffsetForIdOnlyScanMode
public int getMinOffsetForIdOnlyScanMode()For RDBMS, pagination is slow if `offset` is large, especially for MySQL. If `offset` >= $thisArgument
will be automatically changed toselect t.* from Table t ... limit ? offset ?select t.* from ( select t.id as optimized_core_id_ from Table t ... limit ? offset ? ) optimized_core_ inner join Table as optimized_ on optimized_.optimized_core_id_ = optimized_core_.optimized_core_id_- 返回:
- An integer which is greater than 0
-
getExecutorContextPrefixes
If this option is configured, when jimmer calls back `org.babyfish.jimmer.sql.runtime.Executor.execute` before executing SQL, it will check the stack trace information of the current thread. However, these stack traces have too much information, including infrastructure call frames represented by jdk, jdbc driver, jimmer, and spring, and the business-related information you care about will be submerged in the ocean of information. Through this configuration, you can specify multiple package or class prefixes, and jimmer will judge whether there are some call frames in the stack trace whose class names start with some of these prefixes. If the judgment is true, jimmer believes that the current callback is related to your business, and the `ctx` parameter of `org.babyfish.jimmer.sql.runtime.Executor.execute` will be passed as non-null. If the SQL logging configuration is enabled at the same time, when a SQL statement is caused by the business you care about, the business call frame will be printed together with the SQL log. -
getMicroServiceName
-
getClient
-
toString
-