title: What should happend when using a disconnected Sequel::Database object for querying?
body: <p>The situation I'm facing is the following:</p>
  <ol>
  <li>Initialize a database connection:</li>
  </ol>
  <pre class="lang-rb prettyprint-override"><code>DB = Sequel.connect('&lt;my-connection-string&gt;')
  </code></pre>
  <ol start="2">
  <li>Use it for raw queries as usual (SQL in this case):</li>
  </ol>
  <pre class="lang-rb prettyprint-override"><code>DB['SELECT * FROM my-db'].each do |row|
      puts 'It works (as it should)'
  end
  </code></pre>
  <ol start="3">
  <li>Disconnect all the connections from that DB's pool:</li>
  </ol>
  <pre class="lang-rb prettyprint-override"><code>DB.disconnect
  </code></pre>
  <ol start="4">
  <li>Use again the disconnected DB object for querying (without explicitly connecting again):</li>
  </ol>
  <pre class="lang-rb prettyprint-override"><code>DB['SELECT * FROM my-db'].each do |row|
      puts 'It STILL works (I did not expect it)'
  end
  </code></pre>
  <p>As I'm observing in my connections inspector, even after disconnecting, re-using the object ends up in opening a new connection to the same DB the object was initially configured to connect, and everything works just fine.</p>
  <p>I ended up here by configuring a simple connection at <code>initialize</code> time in a class but closing it after each iteration on a loop of queries, and to my surprise it worked fine without any complains.</p>
  <p><strong>My question is</strong>: is this how it is supposed to behave? Is this documented behavior or is just undefined behavior which, due to good design patterns (I guess?) from Sequel's side, ends up in consistent behavior? So far I haven't been able to find anything, neither in <a href="http://sequel.jeremyevans.net/rdoc/" rel="nofollow noreferrer">Sequel's documentation</a> nor in SO.</p>
  <p>I'd like to keep on using this format (since it saves quite a lot of code lines in my specific case), but only if it is something reliable.</p>