On Jan 6, 9:13 am, Jeremy Evans <[email protected]> wrote: > > > Another reason is that implicit reconnection can cause the same > > > statement to be executed twice, leading to problems with non- > > > idempotent statements. > > > I didn't know that - do you know if that is that a general mysql issue > > or just an issue with Sequel? (wondering whether I should be removing > > the reconnect: true option from my various ActiveRecord-related > > projects) > > AFAIK, it's a general issue with how implicit reconnection has to > work. The fact that it's turned off by default should mean something.
I forgot to mention earlier that implicitly reconnection probably doesn't deal well with transactions for obvious reasons. Basically, a database connection has state, and implicitly reconnecting creates a new connection with different state, but there's no way for Sequel (or other database libraries) to know that the state was changed. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
