Concurrency updates and database logging APIs #775
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes are now available in 4.11.0
This update contains the following changes:
Application.db(_:logger:)
andRequest.db(_:logger:)
. These work exactly the way the respective.db(_:)
methods do, except the database's logger will be set to the one provided rather than the default. These APIs will hopefully make it easier to work around the unfortunate fact thatDatabase.logging(to:)
and its SQLKit counterpart basically don't work at all.--auto-migrate
and--auto-revert
commandline flags no longer callEventLoopFuture.wait()
when the app is booted inasync
mode (no more crash risk).migrate
command now has nicer console output.async
.