Breaking Changes
0.51.0
The
exposed-spring-boot-startermodule no longer provides the entire spring-boot-starter-data-jdbc module. It now provides just the spring-boot-starter-jdbc. If there was a reliance on this transitive dependency, please directly include a dependency on Spring Data JDBC in your build files.ulongcolumn type is now NUMERIC(20) instead of BIGINT for H2 (excluding H2_PSQL), SQLite, and SQL Server to allow storing the full range ofULong, includingULong.MAX_VALUE.
0.50.0
The
Transactionclass propertyrepetitionAttemptsis being deprecated in favor ofmaxAttempts. Additionally, the propertyminRepetitionDelayshould be replaced withminRetryDelay, andmaxRepetitionDelaywithmaxRetryDelay. These changes also affect the default variants of these properties inDatabaseConfig.The property
maxAttemptsrepresents the maximum amount of attempts to perform a transaction block. Setting it, or the now deprecatedrepetitionAttempts, to a value less than 1 now throws anIllegalArgumentException.IColumnTypeandColumnTypenow expect a type argument.IColumnType.valueFromDB()also no longer has a default implementation, so an override for this method must be provided in any custom column type implementation. Check this pull request for details regarding this change.
0.49.0
For SQLite database, Exposed now requires bumping the SQLite JDBC driver version to a minimum of 3.45.0.0.
0.48.0
In
nonNullValueToStringforKotlinInstantColumnTypeandJavaDateColumnType, the formatted String for MySQL did not match the format received from the metadata whenisFractionDateTimeSupportedis true, so a new formatter specific to that is now used.In
nonNullValueToStringforKotlinLocalDateTimeColumnType, the formatted String for MySQL did not match the format received from the metadata whenisFractionDateTimeSupportedis true, so a new formatter specific to MySQL is now used.In
nonNullValueToStringforDateColumnType,JavaLocalDateTimeColumnType,JavaLocalTimeColumnType,JavaInstantColumnType,KotlinLocalDateTimeColumnType,KotlinLocalTimeColumnType, andKotlinInstantColumnType, the correct formatter for MySQL is used when the version (below 5.6) does not support fractional seconds.In
nonNullValueToStringforDateColumnTypeandDateTimeWithTimeZoneColumnType, the formatters used are changed to reflect the fact that Joda-Time stores date/time values only down to the millisecond (up to SSS and not SSSSSS).Functions
anyFrom(array)andallFrom(array)now useArrayColumnTypeto process the provided array argument when query building.ArrayColumnTyperequires a base column type to process contents correctly, and Exposed attempts to resolve the best match internally based on the array content type. A specific column type argument should be provided to the function parameterdelegateTypeif the content requires either an unsupported or custom column type, or a column type not defined in theexposed-coremodule.exposed-cryptmodule now uses Spring Security Crypto 6.+, which requires Java 17 as a minimum version.
0.47.0
The function SchemaUtils.checkExcessiveIndices is used to check both excessive indices and excessive foreign key constraints. It now has a different behavior and deals with excessive indices only. Also, its return type is now List<Index> instead of Unit. A new function, SchemaUtils.checkExcessiveForeignKeyConstraints, deals with excessive foreign key constraints and has a return type List<ForeignKeyConstraint>.
0.46.0
When an Exposed table object is created with a keyword identifier (a table or column name) it now retains the exact case used before being automatically quoted in generated SQL. This primarily affects H2 and Oracle, both of which support folding identifiers to uppercase, and PostgresSQL, which folds identifiers to a lower case.
If
preserveKeywordCasing = truehad been previously set inDatabaseConfigto remove logged warnings about any keyword identifiers, this can now be removed as the property istrueby default.To temporarily opt out of this behavior and to not keep the defined casing of keyword identifiers, please set
preserveKeywordCasing = falseinDatabaseConfig:
Exposed 0.51.1 Help
Breaking Changes
0.51.0
The
exposed-spring-boot-startermodule no longer provides the entire spring-boot-starter-data-jdbc module. It now provides just the spring-boot-starter-jdbc. If there was a reliance on this transitive dependency, please directly include a dependency on Spring Data JDBC in your build files.ulongcolumn type is now NUMERIC(20) instead of BIGINT for H2 (excluding H2_PSQL), SQLite, and SQL Server to allow storing the full range ofULong, includingULong.MAX_VALUE.
0.50.0
The
Transactionclass propertyrepetitionAttemptsis being deprecated in favor ofmaxAttempts. Additionally, the propertyminRepetitionDelayshould be replaced withminRetryDelay, andmaxRepetitionDelaywithmaxRetryDelay. These changes also affect the default variants of these properties inDatabaseConfig.The property
maxAttemptsrepresents the maximum amount of attempts to perform a transaction block. Setting it, or the now deprecatedrepetitionAttempts, to a value less than 1 now throws anIllegalArgumentException.IColumnTypeandColumnTypenow expect a type argument.IColumnType.valueFromDB()also no longer has a default implementation, so an override for this method must be provided in any custom column type implementation. Check this pull request for details regarding this change.
0.49.0
For SQLite database, Exposed now requires bumping the SQLite JDBC driver version to a minimum of 3.45.0.0.
0.48.0
In
nonNullValueToStringforKotlinInstantColumnTypeandJavaDateColumnType, the formatted String for MySQL did not match the format received from the metadata whenisFractionDateTimeSupportedis true, so a new formatter specific to that is now used.In
nonNullValueToStringforKotlinLocalDateTimeColumnType, the formatted String for MySQL did not match the format received from the metadata whenisFractionDateTimeSupportedis true, so a new formatter specific to MySQL is now used.In
nonNullValueToStringforDateColumnType,JavaLocalDateTimeColumnType,JavaLocalTimeColumnType,JavaInstantColumnType,KotlinLocalDateTimeColumnType,KotlinLocalTimeColumnType, andKotlinInstantColumnType, the correct formatter for MySQL is used when the version (below 5.6) does not support fractional seconds.In
nonNullValueToStringforDateColumnTypeandDateTimeWithTimeZoneColumnType, the formatters used are changed to reflect the fact that Joda-Time stores date/time values only down to the millisecond (up to SSS and not SSSSSS).Functions
anyFrom(array)andallFrom(array)now useArrayColumnTypeto process the provided array argument when query building.ArrayColumnTyperequires a base column type to process contents correctly, and Exposed attempts to resolve the best match internally based on the array content type. A specific column type argument should be provided to the function parameterdelegateTypeif the content requires either an unsupported or custom column type, or a column type not defined in theexposed-coremodule.exposed-cryptmodule now uses Spring Security Crypto 6.+, which requires Java 17 as a minimum version.
0.47.0
The function SchemaUtils.checkExcessiveIndices is used to check both excessive indices and excessive foreign key constraints. It now has a different behavior and deals with excessive indices only. Also, its return type is now List<Index> instead of Unit. A new function, SchemaUtils.checkExcessiveForeignKeyConstraints, deals with excessive foreign key constraints and has a return type List<ForeignKeyConstraint>.
0.46.0
When an Exposed table object is created with a keyword identifier (a table or column name) it now retains the exact case used before being automatically quoted in generated SQL. This primarily affects H2 and Oracle, both of which support folding identifiers to uppercase, and PostgresSQL, which folds identifiers to a lower case.
If
preserveKeywordCasing = truehad been previously set inDatabaseConfigto remove logged warnings about any keyword identifiers, this can now be removed as the property istrueby default.To temporarily opt out of this behavior and to not keep the defined casing of keyword identifiers, please set
preserveKeywordCasing = falseinDatabaseConfig:
0.44.0
SpringTransactionManagerno longer extendsDataSourceTransactionManager; instead, it directly extendsAbstractPlatformTransactionManagerwhile retaining the previous basic functionality. The class also no longer implements the Exposed interfaceTransactionManager, as transaction operations are instead delegated to Spring. These changes ensure that Exposed's underlying transaction management no longer interferes with the expected behavior of Spring's transaction management, for example, when using nested transactions or with@Transactionalelements likepropagationorisolation.If integration still requires a
DataSourceTransactionManager, please add two bean declarations to the configuration: one forSpringTransactionManagerand one forDataSourceTransactionManager. Then define a composite transaction manager that combines these two managers.If
TransactionManagerfunctions were being invoked by aSpringTransactionManagerinstance, please replace these calls with the appropriate Spring annotation or, if necessary, by using the companion object ofTransactionManagerdirectly (for example,TransactionManager.currentOrNull()).spring-transactionandexposed-spring-boot-startermodules now use Spring Framework 6.0 and Spring Boot 3.0, which require Java 17 as a minimum version.A table that is created with a keyword identifier (a table or column name) now logs a warning that the identifier's case may be lost when it is automatically quoted in generated SQL. This primarily affects H2 and Oracle, both of which support folding identifiers to uppercase, and PostgreSQL, which folds identifiers to a lower case.
To remove these warnings and to ensure that the keyword identifier sent to the database matches the exact case used in the Exposed table object, please set
preserveKeywordCasing = trueinDatabaseConfig:
0.44.0
SpringTransactionManagerno longer extendsDataSourceTransactionManager; instead, it directly extendsAbstractPlatformTransactionManagerwhile retaining the previous basic functionality. The class also no longer implements the Exposed interfaceTransactionManager, as transaction operations are instead delegated to Spring. These changes ensure that Exposed's underlying transaction management no longer interferes with the expected behavior of Spring's transaction management, for example, when using nested transactions or with@Transactionalelements likepropagationorisolation.If integration still requires a
DataSourceTransactionManager, please add two bean declarations to the configuration: one forSpringTransactionManagerand one forDataSourceTransactionManager. Then define a composite transaction manager that combines these two managers.If
TransactionManagerfunctions were being invoked by aSpringTransactionManagerinstance, please replace these calls with the appropriate Spring annotation or, if necessary, by using the companion object ofTransactionManagerdirectly (for example,TransactionManager.currentOrNull()).spring-transactionandexposed-spring-boot-startermodules now use Spring Framework 6.0 and Spring Boot 3.0, which require Java 17 as a minimum version.A table that is created with a keyword identifier (a table or column name) now logs a warning that the identifier's case may be lost when it is automatically quoted in generated SQL. This primarily affects H2 and Oracle, both of which support folding identifiers to uppercase, and PostgreSQL, which folds identifiers to a lower case.
To remove these warnings and to ensure that the keyword identifier sent to the database matches the exact case used in the Exposed table object, please set
preserveKeywordCasing = trueinDatabaseConfig:
0.43.0
In all databases except MySQL, MariaDB, and SQL Server, the
ubyte()column now maps to data typeSMALLINTinstead ofTINYINT, which allows the full range ofUBytevalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUByte.MAX_VALUE. If a column that only uses 1 byte of storage is needed, but without allowing any non-negative values to be inserted, please use a signedbyte()column instead with a manually created check constraint:
0.43.0
In all databases except MySQL, MariaDB, and SQL Server, the
ubyte()column now maps to data typeSMALLINTinstead ofTINYINT, which allows the full range ofUBytevalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUByte.MAX_VALUE. If a column that only uses 1 byte of storage is needed, but without allowing any non-negative values to be inserted, please use a signedbyte()column instead with a manually created check constraint:
In all databases except MySQL and MariaDB, the
uint()column now maps to data typeBIGINTinstead ofINT, which allows the full range ofUIntvalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUInt.MAX_VALUE. If a column that only uses 4 bytes of storage is needed, but without allowing any non-negative values to be inserted, please use a signedinteger()column instead with a manually created check constraint:
In all databases except MySQL and MariaDB, the
uint()column now maps to data typeBIGINTinstead ofINT, which allows the full range ofUIntvalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUInt.MAX_VALUE. If a column that only uses 4 bytes of storage is needed, but without allowing any non-negative values to be inserted, please use a signedinteger()column instead with a manually created check constraint:
0.42.0
SQLite The table column created using
date()now uses TEXT datatype instead of DATE (which the database mapped internally to NUMERIC type). This applies to the specificDateColumnTypein all 3 date/time modules and meansLocalDatecomparisons can now be done directly without conversions.H2, PostgreSQL Using
replace()now throws an exception as the REPLACE command is not supported by these databases. Ifreplace()was being used to perform an insert or update operation, all usages should instead be switched toupsert(). See documentation for UPSERT detailsOperator classes
existsandnotExistshave been renamed toExistsandNotExists. The functionsexists()andnotExists()have been introduced to return an instance of their respectively-named classes and to avoid unresolved reference issues. Any usages of these classes should be renamed to their capitalized forms.customEnumeration()now registers aCustomEnumerationColumnTypeto allow referencing by another column. The signature ofcustomEnumeration()has not changed and table columns initialized using it are still of typeColumn<DataClass>.Transaction.suspendedTransaction()has been renamed toTransaction.withSuspendTransaction(). Please runEdit -> Find -> Replace in files...twice withsuspendedTransaction(andsuspendedTransactionas the search options, to ensure that both variants are replaced without affectingsuspendedTransactionAsync()(if used in code).The
repetitionAttemptsparameter intransaction()has been removed and replaced with a mutable property in theTransactionclass. Please remove any arguments for this parameter and assign values to the property directly:
0.42.0
SQLite The table column created using
date()now uses TEXT datatype instead of DATE (which the database mapped internally to NUMERIC type). This applies to the specificDateColumnTypein all 3 date/time modules and meansLocalDatecomparisons can now be done directly without conversions.H2, PostgreSQL Using
replace()now throws an exception as the REPLACE command is not supported by these databases. Ifreplace()was being used to perform an insert or update operation, all usages should instead be switched toupsert(). See documentation for UPSERT detailsOperator classes
existsandnotExistshave been renamed toExistsandNotExists. The functionsexists()andnotExists()have been introduced to return an instance of their respectively-named classes and to avoid unresolved reference issues. Any usages of these classes should be renamed to their capitalized forms.customEnumeration()now registers aCustomEnumerationColumnTypeto allow referencing by another column. The signature ofcustomEnumeration()has not changed and table columns initialized using it are still of typeColumn<DataClass>.Transaction.suspendedTransaction()has been renamed toTransaction.withSuspendTransaction(). Please runEdit -> Find -> Replace in files...twice withsuspendedTransaction(andsuspendedTransactionas the search options, to ensure that both variants are replaced without affectingsuspendedTransactionAsync()(if used in code).The
repetitionAttemptsparameter intransaction()has been removed and replaced with a mutable property in theTransactionclass. Please remove any arguments for this parameter and assign values to the property directly:
In all databases except MySQL and MariaDB, the
ushort()column now maps to data typeINTinstead ofSMALLINT, which allows the full range ofUShortvalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUShort.MAX_VALUE. If a column that only uses 2 bytes of storage is needed, but without allowing any non-negative values to be inserted, please use a signedshort()column instead with a manually created check constraint:
In all databases except MySQL and MariaDB, the
ushort()column now maps to data typeINTinstead ofSMALLINT, which allows the full range ofUShortvalues to be inserted without any overflow. Registering the column on a table also creates a check constraint that restricts inserted data to the range between 0 andUShort.MAX_VALUE. If a column that only uses 2 bytes of storage is needed, but without allowing any non-negative values to be inserted, please use a signedshort()column instead with a manually created check constraint: