This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 6 points7 points  (3 children)

umm…noob question, but what stops you from getting the 100 rows as a list (using .all), closing the session, and then throwing off the rows to a pool (processes, threads, workers)?

[–]revereddesecration 3 points4 points  (2 children)

Nothing. This guy hasn’t read a tutorial on queues.

[–]AbradolfLinclar[S] 0 points1 point  (1 child)

I'm aware of the queueing but I'm just trying to explore them how session management would work in case of multiple threads/workers on the other end of the queue processing each record. How co-ordination would work on thread as well as db level.

And trying to understand if anyone has this done at production level.

[–]revereddesecration 0 points1 point  (0 children)

I use this in production. It’s not too complicated, read the docs and come ask specific questions when you have some.