@nafg I think we'll be ready to do an RC in about two weeks, and then after that wait a month or so, minimum, before final? maybe longer depending on how the RC is received?
but also, I'm not just trying to get one release out, I'm hoping this can be self-sustaining again going forward, for as long as people are still using the library
What do you want to achieve?
I wanted to implement something like "clean up" actions. Attach an effect to your DBIO, and carry it around with you across all the flatmaps/andthens etc, and then when it is eventually run tack the effects on to the future as a side-effect.
Imagine something like a huge dbio transaction that at some point changes a user's subscription settings. At that point in the DBIO, I know I have to send an email to the user. It would be handy to at that point attach it (the send-email effect) to the DBIO and have it dealt with alongside the transaction execution automatically (if the transaction succeeds)
bit(1)data type for a
min(...)like this example
select min(field1), min(field2), min(myBit1Field) from ... group by id. Unfortunately, that aggregation doesn't play well with mysql's
bit(1)which in my case ends up being
truein my scala object when the record field in DB is 0x00 (false).
also it seems like travis only does one build at a time on the repo
we can live with that, I think...? especially now that my recent branch protection change cut the number of builds per PR from 2 back down to 1