Digest for jooq-user@googlegroups.com - 2 updates in 2 topics

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Digest for jooq-user@googlegroups.com - 2 updates in 2 topics

http://groups.google.com/group/jooq-user/topics mailing list
Marshall Pierce <[hidden email]>: Oct 02 06:22AM -0700

There's little downside to having this exposed as an extension method
(extension methods can only access public members but not an issue here),
and I think that's really the only reasonable way to do it. Technically I
could provide a TransactionalCallable with a runBlocking{} inside it, and
that would compile, but also lose much of the benefits of using coroutines
(won't carry over coroutine context, ties up a thread). Instead, I threw
together a quick proof of concept of one way it could work:
https://github.com/jOOQ/jOOQ/compare/master...marshallpierce:kotlin-suspend-txn-result?expand=1
 
This way does work and was "easy", but now there's essentially a duplicated
copy of `transactionResult0`, which is pretty sad, and it's in
`org.jooq.impl` to get access to DefaultTransactionContext and friends,
creating a split package which will make JPMS upset.
 
If there was another way to implement the listener stuff before and
exception stuff after that didn't involve package-private classes (and
hopefully also avoiding copy-and-paste code...), then the extension
function could be in a separate package, and indeed a separate project
entirely. Or, if there isn't an option to use public types, could *gasp*
actually use JPMS to expose the org.jooq.impl package to
org.jooq.kotlin_stuff_goes_here. Mark Reinhold would be so happy.
 
On Tuesday, October 1, 2019 at 12:47:38 AM UTC-6, Lukas Eder wrote:
[hidden email]: Oct 02 04:05AM -0700

On Monday, September 30, 2019 at 6:47:36 AM UTC, Lukas Eder wrote:
> directly, using Derby's default case (UPPER CASE), and then request data
> from quoted "lower case" identifiers. You have several ways to work around
> this:
 
Thanks, this makes sense!
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].