Saurabh Nanda

@tchoutri added the changelog entry - hope it's fine.

@tchoutri please give me a day -- I just got back from vacation. Will update the PR.

@jappeace @ivb-supercede any thoughts on this functionality / feature? Few notes: - makes sense only when completed jobs are deleted after a delay. This allows an end-user/UI to trigger a...

Folks, this has a breaking change in the library's external API. Is everyone largely fine with this? @jappeace @tfausak @tchoutri (please tag other active users, as well)

@jappeace @tfausak one way to not break any existing code would be to have a build-time flag along with liberal use of CPP at the following places: - `OddJobs.Types.Job` data...

> I was thinking along the lines of: instead of changing this function in place, we add a new one and see if it can be made compatable, @jappeace I...

I think the two **DB columns** that all users of the library are going to be forced to create are a greater problem than the Haskell code.... any ideas on...

@tchoutri @jappeace @tfausak what do you feel about the current attempt on making this backward compatibly and purely opt-in?

> @saurabhnanda those modules are provisional workarounds, they're not intended to grow any more than necessary. I wanted a way to deal with the random()/rand() split. Anything that works in...

@harendra-kumar 1. That version of streamly is what comes with Stack LTS 18.28 -- we haven't upgrade out entire toolchain because this seems to be working fine atm 2. https://hackage.haskell.org/package/opaleye-0.6.1.0/docs/src/Opaleye-RunQuery.html#runQueryFold...