You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually support query logging (#225)
* Support query log levels. Also fix some Sendable stuff.
* Use logging metadata for logging the transaction control queries
Shut down the driver's connection pool safely (#224)
* Update required versions of dependencies
* Shut down the EventLoopGroupConnectionPool using an API that doesn't call EventLoopFuture.wait() internally.
Update package for Sendable and 100% test coverage (#223)
* Package structure, CI, and docs updates. Min Swift updated to 5.8.
* Add Sendable and ExistentialAny correctness. Fix forwarding of data encoder/decoders to the SQLKit layer. Add support for new SQLKit functionality. Throw DecodingErrors instead of fatalErrors(). Remove unused properties and files.
* Add 100% documentation coverage
* Achieve 100% test coverage. Make tests async and Sendable-correct. Add missing FluentBenchmark test set. Use singleton ELG and thread pool for tests.
* Add updated repo logo
Update for the nested subpath changes in FluentKit (#218)
Remove no longer needed (well, never needed, really) nested subpath support in SQL converter delegate. General tidying and CI.
Update min Swift version to 5.6 and make platform versions consistent (……#217)
Update minimum Swift version to 5.6 and make platform versions consistent.
Drop support for Swift 5.4 (#214)
* Drop support for Swift 5.4
* Minor CI overhaul - add code coverage, add API breakage check, update Swift versions, use common environment, narrow matrix of DB server versions except when meaningful, use generic naming int default param values, don't explicitly drop and recreate DBs in tests
Explicitly handle a custom ID key set to the empty string (#210)
* Add the composite ID benchmark tests.
* Drop support for Swift 5.2 and 5.3
* Require current version of Fluent
DatabaseError's `isSyntaxError` and `isConnectionClosed` properties n…
…ow correctly respect `MySQLError.invalidSyntax` and `MySQLError.closed`. A unit tests for these behaviors is included. (#203)
Also avoids double-running the FluentBenchmark tests and adds the missing `testSQL()` benchmark test.