All Versions
85
Latest Version
Avg Release Cycle
-
Latest Release
-
Changelog History
Page 5
Changelog History
Page 5
-
v3.4.2 Changes
Migration Notes:
NamingStrategy
is no longer applied on column and table names defined inquerySchema
, all column and table names defined inquerySchema
are now final. If you are relying on this behavior to โก๏ธ name your columns/tables correctly, you will need to update yourquerySchema
objects.
-
v3.4.1 Changes
Migration Notes:
- Nested sub-queries will now have their terms re-ordered in certain circumstances although the functionality ๐ of the entire query should not change. If you have deeply nested queries with Infixes, double check that they are in the correct position.
-
v3.4.0 Changes
Migration Notes:
- 0๏ธโฃ Infixes are now not treated as pure functions by default. This means wherever they are used, nested queries may be created.
You can use
.pure
(e.g.infix"MY_PURE_UDF".pure.as[T]
) to revert to the previous behavior. See the Infix ๐ section of the documentation for more detail.
- 0๏ธโฃ Infixes are now not treated as pure functions by default. This means wherever they are used, nested queries may be created.
You can use
-
v3.3.0 Changes
- Returning Record
- Change == and != to be Scala-idiomatic
- โก๏ธ Optimize === comparisons when ANSI behavior assumed
- API to get PreparedStatement from Query for Low Level Use-cases
- ๐ Add BoundStatement support for all context.
- Only decode when field is non-null
- ๐ Fix support of nested transactions in Finagle-Postgres
- Returning shadow fix
- Fix SQL Server Subqueries with Order By
- Explicitly pass AsyncContext type params
- ๐ Remove unneeded Tuple reduction clause
- Fix join subquery+map+distinct and sortBy+distinct
- Fix Java9 depreciation message
Noteworthy Version Bumps:
- monix - 3.0.0-RC3
- cassandra-driver-core - 3.7.2
- orientdb-graphdb - 3.0.21
- postgresql - 42.2.6
- sqlite-jdbc - 3.28.0
Migration Notes:
- The
returning
method no long excludes the specified ID column from the insertion as it used to. ๐ Use thereturningGenerated
method in order to achieve that. ๐ See the 'Database-generated values' section of the documentation for more detail. - The
==
method now works Scala-idiomatically. That means that when twoOption[T]
-wrapped columns are compared,None == None
will now yieldtrue
. The===
operator can be used in order to compareOption[T]
-wrapped columns in a ANSI-SQL ๐ idiomatic way i.e.None == None := false
. See the 'equals' section of the documentation for more detail.