Hi Jeremy, Thats really a good idea, thanks!
I noticed that there is a Sequel::DATABASES array which keeps all references to connections made without a block. With the multi tenant environment in mind, its a good practice to look through this object before make a new connection to check if there is one already? ][`s Em sexta-feira, 27 de julho de 2018 20:18:13 UTC-3, Jeremy Evans escreveu: > > On Friday, July 27, 2018 at 2:40:04 PM UTC-7, Renato Alves wrote: >> >> Hi Jeremi, >> Thanks for your answer! >> >> We are building a service like Chart.io, where customer pass their >> Database Connectiosn. Its a multi tenant application, so we created >> Database Connections at runtime because we have to validate database, >> connections, etc. >> >> In this case, do you think Sequel a bad option, or you think there is >> another way? >> > > In this case, you should pass a block when creating the database, so it > will disconnect and remove the internal reference after the block exits. > Alternatively, you can use the :keep_reference=>false option when creating > the database connection, so Sequel doesn't keep an internal reference to > it. When using the :keep_reference=>false option, you should also call > Database#disconnect manually after you are done using the Database instance. > > Thanks, > Jeremy > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
