Yes I've read the documentation several times and it is unclear. "Before checkout" isn't evident and leads me to believe it's at the end of a connection. Why it would check the connection pool at the end of a connection is strange as I would expect the flushing of the pool would occur at the onset of a demand of a connection, regardless if the pool has valid open connections or not. This is why I'm confused.
Just now, bringing up the page again after 8 hours (which is over the stated default value of 1 hour), it happened again. So the syntax I have in there, directly after the declaration of that constant (Sequel::Database connection), wouldn't it check the pool only to find no valid live connections. Would it see the pool as empty and initiate a new connection? At this point I'm thinking these errors are from entries in the pool that are not open anymore. And I thought the syntax provided would have flushed the pool upon a morning entry (my example internal website serves me only, so it's idle overnight). The last request at the end of the day would update the single connection in the pool. One hour later, it expires (or is considered expired by Sequel's default value). It will eventually close, as is shown by the error. I am under the impression that this is used at the beginning of a new session in the morning, hence the placement right behind the declaration. I'm not clear on what I'm missing. This isn't about < 60 minutes vs > 60 minutes. This is showing up on something 10 hours idle. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/b1133b93-33e1-47e3-aaa5-e085e80f330a%40googlegroups.com.
