Blake Gentry

Hi @atoi, this is actually intentional, although it should have been documented. I pushed up a commit that demonstrates this behavior and documents it [here](https://github.com/riverqueue/river/compare/bg-add-test-for-job-args-type-metadata-being-ignored). I'm wondering what use case...

@dyeje can you add any context around what you were seeing, what your workload is like, jobs/sec or day, etc?

Ah, I’m glad I asked because this jogged my memory on something we are missing here. It would be a bit of a misuse of metadata it was used for...

Hi @mgdigital, there are a couple of challenges to work through here: 1. Although River has a concept of "drivers", this was a last-minute addition and you can probably see...

Hi @arp242, wanted to make sure you’ve seen that River now has a database/sql driver. Here’s the doc on using that with GORM: https://riverqueue.com/docs/gorm I guess we forgot to mark...

@arp242 ah yep, I think #352 is one possible approach there. To your point we _have_ the underlying fully-capable pgx connection here, all we need is to teach the `database/sql`...

Hi, thanks for reporting this! Can you provide some additional info to help us track down the source of this regression? * Which version of River were you on previously?...

@malonaz ah, I may have misinterpreted this report initially. This `CompleteDuration` stat should have nothing to do with the changes to the `LISTEN`/`NOTIFY` mechanism. This stat is measuring the time...

@malonaz haven't heard anything back on whether or not you still believe there's an issue here, though I think it's mostly a matter of how the durations were being measured....

Please check out the job insertion and worker middleware added in #632 / v0.13.0-rc.1. I believe that should solve the use cases I'm aware of here. Please also report back...