Releases: vapor/database-kit
DatabaseKit 1.3.3
DatabaseKit 1.3.2
Fixed:
- Fixed an error that could cause connection pool to be exhausted when creating new connections failed. (#51)
DatabaseKit 1.3.1
Fixed:
Previously, the max connections per pool would default to System.coreCount
. This could create hanging request issues on some Linux deploys where the core count was 1
.
If a max of 10
is too high, you can still of course configure this to any value you want using the following snippet during service configuration.
services.register { container in
return DatabaseConnectionPoolConfig(maxConnections: 5)
}
DatabaseKit 1.3.0
DatabaseKit 1.2.0
New:
- Adds
DatabaseQueryable
protocol for uniting DB query APIs across drivers (#39).
DatabaseKit 1.1.0
New:
DatabaseConnection
now has an associated database type (#38).
Database Kit 1.0.1
Fixed:
- Added deprecations for
requestConnection(...)
andreleaseConnection(...)
extensions onContainer
.
Milestone:
1.0.1
Database Kit 1.0.0
Introducing Database Kit 1.0 🎉
🗄 Core services for creating database integrations.
Docs:
https://docs.vapor.codes/3.0/database-kit/getting-started/
API Docs:
https://api.vapor.codes/database-kit/latest/DatabaseKit
Changes since last RC:
New:
ConfiguredDatabase
type for more consistent connection configuration.DatabaseKeyedCache
type replaces Fluent keyed cache.
Fixed:
DatabaseConfig
renamed toDatabasesConfig
to make it clear that it is for configuring multiple dbs.withConnection(...)
renamed towithNewConnection(...)
to better distinguish it from the pooled methods.
Milestone:
1.0.0
DatabaseKit 1.0.0 RC 2.2.1
New:
- Added a
databaseName
property toURL
.
API Docs:
https://api.vapor.codes/database-kit/1.0.0-rc.2.2.1/DatabaseKit/
https://api.vapor.codes/database-kit/1.0.0-rc.2.2.1/SQL/
Database Kit 1.0.0 RC 2.1.1
Fixed:
- Fixed an issue where IN/NOT-IN predicates with 0 or 1 values would serialize incorrectly.
Milestone:
1.0.0-rc.2.1.1