Am 14.04.2010 um 21:47 schrieb Alex Karpinski:
Is there any way to avoid having to follow that commit() up the threads? My main thread is waiting on socket connections and can't be trusted to commit any time I want. For convenience's sake on a number of levels I'd really like to just be able to have independent database interactions for some threads. Is that at all possible or reasonable?
It has not much to do with elixir, more with the way databases work. If you use transactions, you gotta use them. You can try & set the session to autocommit, that should help.
However, I don't see (from the little bit of information you gave so far, so this is guesswork of course) why your main-thread can't commit. If you have an event-loop that waits for connections - well, once you got one, commit to see what has changed, work on that dataset until you drop into the event-loop gain, and that's it.
Diez -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en.
