Ruby 3.1 will make ruby fiber scheduler, which introduced in ruby 3.0, the official non-block io and concurrency solution, more mature and completely, but, as mention by Samuel Williams @ioquatix, who is the author of async, in this video.
https://youtu.be/Y29SSOS4UOc?list=LL&t=1406 activerecord use one connection per thread, because of this, multiple independent fiber on the same thread will be using the same underlying connection, this can cause problems because multiple fibers could incorrectly share a transaction, this is kind of a design fault of activerecord. so, i just curious if sequel exists a similar issue, and if is, if there is a plan to solve this, and how to do it. Thank you. -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to sequel-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/c2d3142b-22bf-4aed-a540-ec0b748b597cn%40googlegroups.com.
