Tuesday, July 2, 2019
ActiveRecord::Base.remove_connection disconnects all connections to the database. ActiveRecord might reconnect on subsequent queries, but this is not what I want, I want to reuse already open connections for performance.
To be clear, I know how to make the above code work (I can call ActiveRecord::Base.clear_active_connections!, or ActiveRecord::Base.connection_pool.with_connection with a block), what I'm challenging is that ActiveRecord shouldn't require that you manually release connections back into the pool (like Sequel doesn't).
On 2 Jul 2019, 17:48 +0200, botp <botpena@gmail.com>, wrote:
On 7/2/19, Janko Marohnić <janko.marohnic@gmail.com> wrote:
10.times do
threads << Thread.new do
ActiveRecord::Base.connection.execute "SELECT 1"
try also remove_connection
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAAwHHQhefaNNg_Pw3ywUYQqKXQBWCjET-24emFnX%2B6%2BO2xQ0RQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment