Closed vemv closed 2 years ago
Great justification -- thank you!
Cheers 🍻 would appreciate a release!
You can use a SNAPSHOT :) https://clojars.org/com.github.seancorfield/next.jdbc/versions/1.2.999-SNAPSHOT
Not ideal in my work setting. Sorry to bother!
1.2.796 is up on Clojars.
Thank you!
On Mon, Aug 1, 2022 at 7:01 PM Sean Corfield @.***> wrote:
1.2.796 is up on Clojars.
— Reply to this email directly, view it on GitHub https://github.com/seancorfield/next-jdbc/pull/209#issuecomment-1201470451, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI354QB5STMNB62IISJC5TVW77HTANCNFSM55F4FOBA . You are receiving this because you authored the thread.Message ID: @.***>
This is the only missing piece for a metadata-based no-op Component, which I want for tests that must not hit a database, yet still realistically hit the next.jdbc code as used throughout my codebase.
In specific terms, I have a scenario that looks approximately like this:
In other words, I want to have a simple app-specific protocol for sql interactions, while still being able to use
with-transaction
. So bespoke implementations have to implement not only Sourceable, but also Transactable.(note that I cannot create an application-specific protocol for a macro - macros aren't protocol-able)
I hope you appreciate the highly realistic example. IIRC you don't like to add
:extend-via-metadata true
where not needed.Cheers - V