dbmlite3 2.0.0.pre.alpha.6 → 2.0.1

data/doc/Lite3/Error.html

@@ -6,7 +6,7 @@
 <title>
   Exception: Lite3::Error
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -129,9 +129,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:55 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:43 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/Lite3/InternalError.html

@@ -6,7 +6,7 @@
 <title>
   Exception: Lite3::InternalError
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -133,9 +133,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:55 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:43 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/Lite3/SQL.html

@@ -6,7 +6,7 @@
 <title>
   Module: Lite3::SQL
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -220,10 +220,10 @@
       <pre class="lines">
 
 
-84</pre>
+87</pre>
     </td>
     <td>
-      <pre class="code"><span class="info file"># File 'lib/internal_lite3/sql.rb', line 84</span>
+      <pre class="code"><span class="info file"># File 'lib/internal_lite3/sql.rb', line 87</span>
 
 <span class='kw'>def</span> <span class='kw'>self</span><span class='period'>.</span><span class='id identifier rubyid_close_all'>close_all</span><span class='lparen'>(</span><span class='rparen'>)</span>    <span class='kw'>return</span> <span class='const'>HandlePool</span><span class='period'>.</span><span class='id identifier rubyid_close_all'>close_all</span>     <span class='kw'>end</span></pre>
     </td>
@@ -245,9 +245,9 @@
     
 <p>Disconnect and delete all database handles and associated metadata that are no longer needed (i.e. because their corresponding <code>DBM</code>s have been closed or reclaimed).</p>
 
-<p>Returns a hash mapping the path to each open database file to the number of live DBM objects referencing it.</p>
+<p>Returns a hash mapping the path to each open database file to the number of live DBM objects referencing it. (Note that DBM objects that have gone out of scope but are not yet finalized count as “live”; as a result, this will differ across Ruby implementations due to differing garbage collector semantics.)</p>
 
-<p>You normally won&#39;t need to explicitly call this, but it&#39;s useful for testing and debugging.</p>
+<p>You normally won’t need to explicitly call this, but it’s useful for testing and debugging.</p>
 
 
   </div>
@@ -261,10 +261,10 @@
       <pre class="lines">
 
 
-71</pre>
+74</pre>
     </td>
     <td>
-      <pre class="code"><span class="info file"># File 'lib/internal_lite3/sql.rb', line 71</span>
+      <pre class="code"><span class="info file"># File 'lib/internal_lite3/sql.rb', line 74</span>
 
 <span class='kw'>def</span> <span class='kw'>self</span><span class='period'>.</span><span class='id identifier rubyid_gc'>gc</span><span class='lparen'>(</span><span class='rparen'>)</span>           <span class='kw'>return</span> <span class='const'>HandlePool</span><span class='period'>.</span><span class='id identifier rubyid_gc'>gc</span><span class='semicolon'>;</span>           <span class='kw'>end</span></pre>
     </td>
@@ -333,9 +333,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:55 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/Lite3.html

@@ -6,7 +6,7 @@
 <title>
   Module: Lite3
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -109,9 +109,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:54 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/_index.html

@@ -4,7 +4,7 @@
     <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
 <title>
-  Documentation by YARD 0.9.26
+  Documentation by YARD 0.9.34
   
 </title>
 
@@ -52,7 +52,7 @@
         <div class="clear"></div>
       </div>
 
-      <div id="content"><h1 class="noborder title">Documentation by YARD 0.9.26</h1>
+      <div id="content"><h1 class="noborder title">Documentation by YARD 0.9.34</h1>
 <div id="listing">
   <h1 class="alphaindex">Alphabetic Index</h1>
   
@@ -157,9 +157,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:54 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/file.README.html

@@ -6,7 +6,7 @@
 <title>
   File: README
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -139,7 +139,7 @@ $ rake
 <pre class="code ruby"><code class="ruby"><span class='id identifier rubyid_db'>db</span><span class='lbracket'>[</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>foo</span><span class='tstring_end'>&#39;</span></span><span class='rbracket'>]</span> <span class='op'>+=</span> <span class='int'>1</span>
 </code></pre>
 
-<p>contains a race condition. If (e.g.) two copies of this script are running at the same time, it is possible for both to perform the read before one of them writes, losing the others&#39; result.</p>
+<p>contains a race condition. If (e.g.) two copies of this script are running at the same time, it is possible for both to perform the read before one of them writes, losing the others’ result.</p>
 
 <p>There are two ways to deal with this. You can wrap the read-modify-write cycle in a transaction:</p>
 
@@ -190,26 +190,26 @@ $ rake
 
 <p>While it is generally safe to treat <code>Lite3::DBM</code> as a wrapper around a file handle (i.e. <code>open</code> and <code>close</code> work as expected), you should be aware that this is not precisely the way things actually work. Instead, the gem maintains a pool of database handles, one per file, and associates them with <code>Lite3::DBM</code> instances as needed. This is necessary for transactions to work correctly.</p>
 
-<p>Mostly, you don&#39;t need to care about this. However, it affects you in the following ways:</p>
+<p>Mostly, you don’t need to care about this. However, it affects you in the following ways:</p>
 <ol><li>
 <p>Transactions are done at the file level and not the table level.  This means that you can access separate tables in the same  transaction, which is a Very Good Thing.</p>
 </li><li>
-<p>You can safely fork the current process and keep using existing  <code>DBM</code> objects in both processes, provided you&#39;ve invoked  <code>Lite3::SQL.close_all</code> before the fork. This will have closed the  actual database handles (which can&#39;t tolerate being carried across  a fork) and opens new ones the next time they&#39;re needed.</p>
+<p>You can safely fork the current process and keep using existing  <code>DBM</code> objects in both processes, provided you've invoked  <code>Lite3::SQL.close_all</code> before the fork. This will have closed the  actual database handles (which can't tolerate being carried across  a fork) and opens new ones the next time they're needed.</p>
 </li></ol>
 
-<p><code>DBM</code> objects that go out of scope without first being closed <strong>will</strong> eventually have their underlying resources cleaned up. However, given that <em>when</em> when that happens depends on the vagaries of the garbage collector and various library internals, it&#39;s almost always a bad idea to not explicitly call <code>close</code> first.</p>
+<p><code>DBM</code> objects that go out of scope without first being closed <strong>will</strong> eventually have their underlying resources cleaned up. However, given that <em>when</em> when that happens depends on the vagaries of the garbage collector and various library internals, it’s almost always a bad idea to not explicitly call <code>close</code> first.</p>
 
 <h3 id="label-Under+the+hood">Under the hood</h3>
 
 <p>Currently, <code>Lite3::DBM</code> uses <a href="https://sequel.jeremyevans.net">Sequel</a> to access the <code>sqlite3</code> library. On JRuby, it goes through the <code>jdbc</code> interface. The previous version (1.0.0) used <a href="https://github.com/sparklemotion/sqlite3-ruby">sqlite3</a> and only worked on MRI. However, you should make no assumptions about the underlying database libraries this gem uses. It may change in a future release.</p>
 
-<p>All tables created by <code>Lite3::DBM</code> will have names beginning with <code>dbmlite3_</code> and you should not modify them directly. It <strong>might</strong> be safe to put other tables in the same database file (e.g. via <code>Sequel</code>) provided that you don&#39;t make global changes or mix transactions across interfaces. However, I make no guarantees.</p>
+<p>All tables created by <code>Lite3::DBM</code> will have names beginning with <code>dbmlite3_</code> and you should not modify them directly. It <strong>might</strong> be safe to put other tables in the same database file (e.g. via <code>Sequel</code>) provided that you don’t make global changes or mix transactions across interfaces. However, I make no guarantees.</p>
 </div></div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:54 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/frames.html

@@ -2,7 +2,7 @@
 <html>
 <head>
   <meta charset="utf-8">
-	<title>Documentation by YARD 0.9.26</title>
+	<title>Documentation by YARD 0.9.34</title>
 </head>
 <script type="text/javascript">
   var match = unescape(window.location.hash).match(/^#!(.+)/);

data/doc/index.html

@@ -6,7 +6,7 @@
 <title>
   File: README
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -139,7 +139,7 @@ $ rake
 <pre class="code ruby"><code class="ruby"><span class='id identifier rubyid_db'>db</span><span class='lbracket'>[</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>foo</span><span class='tstring_end'>&#39;</span></span><span class='rbracket'>]</span> <span class='op'>+=</span> <span class='int'>1</span>
 </code></pre>
 
-<p>contains a race condition. If (e.g.) two copies of this script are running at the same time, it is possible for both to perform the read before one of them writes, losing the others&#39; result.</p>
+<p>contains a race condition. If (e.g.) two copies of this script are running at the same time, it is possible for both to perform the read before one of them writes, losing the others’ result.</p>
 
 <p>There are two ways to deal with this. You can wrap the read-modify-write cycle in a transaction:</p>
 
@@ -190,26 +190,26 @@ $ rake
 
 <p>While it is generally safe to treat <code>Lite3::DBM</code> as a wrapper around a file handle (i.e. <code>open</code> and <code>close</code> work as expected), you should be aware that this is not precisely the way things actually work. Instead, the gem maintains a pool of database handles, one per file, and associates them with <code>Lite3::DBM</code> instances as needed. This is necessary for transactions to work correctly.</p>
 
-<p>Mostly, you don&#39;t need to care about this. However, it affects you in the following ways:</p>
+<p>Mostly, you don’t need to care about this. However, it affects you in the following ways:</p>
 <ol><li>
 <p>Transactions are done at the file level and not the table level.  This means that you can access separate tables in the same  transaction, which is a Very Good Thing.</p>
 </li><li>
-<p>You can safely fork the current process and keep using existing  <code>DBM</code> objects in both processes, provided you&#39;ve invoked  <code>Lite3::SQL.close_all</code> before the fork. This will have closed the  actual database handles (which can&#39;t tolerate being carried across  a fork) and opens new ones the next time they&#39;re needed.</p>
+<p>You can safely fork the current process and keep using existing  <code>DBM</code> objects in both processes, provided you've invoked  <code>Lite3::SQL.close_all</code> before the fork. This will have closed the  actual database handles (which can't tolerate being carried across  a fork) and opens new ones the next time they're needed.</p>
 </li></ol>
 
-<p><code>DBM</code> objects that go out of scope without first being closed <strong>will</strong> eventually have their underlying resources cleaned up. However, given that <em>when</em> when that happens depends on the vagaries of the garbage collector and various library internals, it&#39;s almost always a bad idea to not explicitly call <code>close</code> first.</p>
+<p><code>DBM</code> objects that go out of scope without first being closed <strong>will</strong> eventually have their underlying resources cleaned up. However, given that <em>when</em> when that happens depends on the vagaries of the garbage collector and various library internals, it’s almost always a bad idea to not explicitly call <code>close</code> first.</p>
 
 <h3 id="label-Under+the+hood">Under the hood</h3>
 
 <p>Currently, <code>Lite3::DBM</code> uses <a href="https://sequel.jeremyevans.net">Sequel</a> to access the <code>sqlite3</code> library. On JRuby, it goes through the <code>jdbc</code> interface. The previous version (1.0.0) used <a href="https://github.com/sparklemotion/sqlite3-ruby">sqlite3</a> and only worked on MRI. However, you should make no assumptions about the underlying database libraries this gem uses. It may change in a future release.</p>
 
-<p>All tables created by <code>Lite3::DBM</code> will have names beginning with <code>dbmlite3_</code> and you should not modify them directly. It <strong>might</strong> be safe to put other tables in the same database file (e.g. via <code>Sequel</code>) provided that you don&#39;t make global changes or mix transactions across interfaces. However, I make no guarantees.</p>
+<p>All tables created by <code>Lite3::DBM</code> will have names beginning with <code>dbmlite3_</code> and you should not modify them directly. It <strong>might</strong> be safe to put other tables in the same database file (e.g. via <code>Sequel</code>) provided that you don’t make global changes or mix transactions across interfaces. However, I make no guarantees.</p>
 </div></div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:54 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/doc/top-level-namespace.html

@@ -6,7 +6,7 @@
 <title>
   Top Level Namespace
   
-    &mdash; Documentation by YARD 0.9.26
+    &mdash; Documentation by YARD 0.9.34
   
 </title>
 
@@ -100,9 +100,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Mar  8 13:02:54 2023 by
-  <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.26 (ruby-3.0.1).
+  Generated on Sat Mar 30 16:15:42 2024 by
+  <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
+  0.9.34 (ruby-3.2.1).
 </div>
 
     </div>

data/lib/internal_lite3/dbm.rb

@@ -1,6 +1,6 @@
 
 module Lite3
-  
+
   # Lite3::DBM encapsulates a single table in a single SQLite3
   # database file and lets you access it as easily as a Hash.
   # Multiple instances may be opened on different tables in the same
@@ -87,9 +87,10 @@ module Lite3
     end
 
 
-    # Identical to `initialize` except that if a block is provided, it
-    # is evaluated with a new Lite3::DBM which is then closed afterward.
-    # This is analagous to `File.open`.
+    # Identical to `new` except that if a block is provided, it is
+    # evaluated with a new Lite3::DBM which is then closed afterward.
+    # This is analagous to `File.open`.  See `initialize` for an
+    # explanation of the arguments and caveats.
     def self.open(filename, tablename, serializer = :yaml, &block)
       instance = self.new(filename, tablename, serializer)
       return instance unless block
@@ -267,15 +268,16 @@ module Lite3
     #
     # `key` **must** be a String or a Symbol; Symbols are
     # transparently converted to Strings.
-    # 
-    # If it is not present and a block is given, evaluate the block
-    # with the key as its argument and return that.
     #
-    # If no block was given either but one extra parameter was given,
-    # that value is returned instead.
+    # If it is not present and a block is given, evaluate the block
+    # with the key as its argument and return that.  If no block was
+    # given either but one extra parameter was given, that value is
+    # returned instead.  Finally, if none of these was given, it
+    # throws an `IndexError` exception.
     #
-    # Finally, if none of these was given, it throws an `IndexError`
-    # exception.
+    # All database accesses occur within a transaction, so it is safe
+    # to consider `fetch` atomic.  This includes evaluating a block
+    # argument.
     #
     # It is an error if `fetch` is called with more than two arguments.
     #
@@ -291,17 +293,21 @@ module Lite3
       # Retrieve the value
       key = check_key(key)
 
-      # Return the value if found.  (nil will always mean the entry
-      # isn't present because values are encoded in strings.)
-      value = @handle.lookup(actual_tbl(), key)
-      return @valdec.call(value) if value
+      # We do the lookup-and-maybe-replace in a transaction so that
+      # it's atomic.
+      transaction do
+        # Return the value if found.  (nil will always mean the entry
+        # isn't present because values are encoded in strings.)
+        value = @handle.lookup(actual_tbl(), key)
+        return @valdec.call(value) if value
 
-      # Not found.  If a block was given, evaluate it and return its
-      # result.
-      return default_block.call(key) if default_block
+        # Not found.  If a block was given, evaluate it and return its
+        # result.
+        return default_block.call(key) if default_block
 
-      # Next, see if we have a default value we can return
-      return args[0] if args.size > 0
+        # Next, see if we have a default value we can return
+        return args[0] if args.size > 0
+      end
 
       # And if all else fails, raise an IndexError.
       raise IndexError.new("key '#{key}' not found.")
@@ -370,7 +376,7 @@ module Lite3
       }
     end
 
-    
+
     # Calls the given block with each key-value pair in the usual
     # order, then return self.  The entire call takes place in its own
     # transaction.

data/lib/internal_lite3/error.rb

@@ -10,18 +10,14 @@ module Lite3
 
   private
 
-  
   module ErrUtil
-
     # Error check: if block evaluates to false, raise a Lite3::DBM::Error
     # with the given message.
     def check(message, &block)
       return if block && block.call
       raise InternalError.new(message)
     end
-    
   end
 
-
   private_constant :ErrUtil
 end

data/lib/internal_lite3/handle.rb

@@ -41,7 +41,7 @@ module Lite3
     end
     alias inspect to_s
 
-    
+
     #
     # References to the DBM object(s) using this handle.
     #
@@ -85,7 +85,7 @@ module Lite3
     #
     # Transactions
     #
-    
+
     # Perform &block in a transaction.  See DBM.transaction.
     def transaction(&block)
       result = nil

data/lib/internal_lite3/sql.rb

@@ -64,7 +64,10 @@ module Lite3
     # corresponding `DBM`s have been closed or reclaimed).
     #
     # Returns a hash mapping the path to each open database file to
-    # the number of live DBM objects referencing it.
+    # the number of live DBM objects referencing it.  (Note that DBM
+    # objects that have gone out of scope but are not yet finalized
+    # count as "live"; as a result, this will differ across Ruby
+    # implementations due to differing garbage collector semantics.)
     #
     # You normally won't need to explicitly call this, but it's
     # useful for testing and debugging.

data/spec/dbmlite3_spec.rb

@@ -5,6 +5,10 @@ require_relative '../lib/dbmlite3.rb'
 require 'fileutils'
 require 'set'
 
+def jruby?
+  return RUBY_PLATFORM == "java"
+end
+
 module Tmp
   @root = File.join( File.dirname(__FILE__), "tmpdata")
   @count = 0
@@ -884,7 +888,8 @@ describe Lite3::SQL do
   }
 
   it "lets you close the actual handle without impeding database use" do
-    expect( Lite3::SQL.gc.size ) .to eq 0
+    jruby? or   # JRuby GC semantics throw this off
+      expect( Lite3::SQL.gc.size ) .to eq 0
 
     file = Tmp.file
     db1 = newbasic.call(file, "first")
@@ -892,14 +897,17 @@ describe Lite3::SQL do
 
     # The above should be using the same handle, which is currently
     # open.
-
-    stats = Lite3::SQL.gc
-    expect( stats.keys.size ) .to eq 1
-
-    # Referencing DBM objects should be db1 and db2
-    path, refs = stats.to_a[0]
-    expect( path ) .to eq file
-    expect( refs ) .to eq 2
+    #
+    # (Depends on GC wierdness so we skip this part for JRuby.)
+    unless jruby?
+      stats = Lite3::SQL.gc
+      expect( stats.keys.size ) .to eq 1
+
+      # Referencing DBM objects should be db1 and db2
+      path, refs = stats.to_a[0]
+      expect( path ) .to eq file
+      expect( refs ) .to eq 2
+    end
 
     # We can no longer test if the underlying file handles are still
     # open, so we don't.
@@ -915,7 +923,8 @@ describe Lite3::SQL do
     db1.close
     db2.close
 
-    expect( Lite3::SQL.gc.keys.size ) .to eq 0
+    jruby? or
+      expect( Lite3::SQL.gc.keys.size ) .to eq 0
   end
 
   it "allows multiple table accesses in the same transaction" do
@@ -978,6 +987,7 @@ describe Lite3::SQL do
     #
     # (Dropping into the debugger after GC.start seems to help.)
 
+    skip "JRuby GC is capricious" if jruby?
 
     file = Tmp.file
     db1 = newbasic.call(file, "first")
@@ -1017,6 +1027,7 @@ end
 
 describe self do
   it "(this test) closes all handles when done with them" do
+    skip "JRuby GC is capricious"if jruby?
     expect( Lite3::SQL.gc.size ) .to eq 0
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dbmlite3
 version: !ruby/object:Gem::Version
-  version: 2.0.0.pre.alpha.6
+  version: 2.0.1
 platform: ruby
 authors:
 - Chris Reuter
-autorequire:
+autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-02-21 00:00:00.000000000 Z
+date: 2024-03-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sequel
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 5.65.0
+        version: 5.71.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 5.65.0
+        version: 5.71.0
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
@@ -87,7 +87,7 @@ description: |2
       (almost) any Ruby type to be stored.  In addition, there is
       rudimentary support for transactions with emphasis on simplicity
       and safety.
-email: chris@isplitonyourgrave.com
+email: chris@remove-this-part.blit.ca
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -116,7 +116,6 @@ files:
 - doc/js/jquery.js
 - doc/method_list.html
 - doc/top-level-namespace.html
-- extras/benchmark.rb
 - lib/dbmlite3.rb
 - lib/internal_lite3/dbm.rb
 - lib/internal_lite3/error.rb
@@ -128,7 +127,7 @@ homepage: https://codeberg.org/suetanvil/dbmlite3
 licenses:
 - MIT
 metadata: {}
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -139,13 +138,13 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.7.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements:
 - Sequel, sqlite3, Ruby MRI
-rubygems_version: 3.2.15
-signing_key:
+rubygems_version: 3.5.4
+signing_key: 
 specification_version: 4
 summary: A DBM-style key-value store using SQLite3
 test_files: []