Hi, Thanks for the bug report. I'll fix the issue with the `integrity_check` and create a new release. Are you calling `auto_vacuum` in any of your code? I see it implemented in the gem, but it doesn't actually seem to be used by anything right now.
As a work-around, just downgrade to version 1.3.11 until I can ship 1.3.13. > On Nov 17, 2016, at 2:43 PM, [email protected] wrote: > > Ruby version 2.3.0 > SQLite 3 gem version 1.3.12 > SQLite3 version 3.15.0 > > I have a program that's been using the SQLite3 gem for a number of years. > It's been running on this version of ruby for a long time too. It runs as > part of the mail delivery pipeline (by dovecot): > > All of a sudden I'm seeing the following in my mail log: > > /usr/local/lib/ruby/gems/2.3.0/gems/sqlite3-1.3.12/lib/sqlite3/pragmas.rb:301: > warning: method redefined; discarding old integrity_check > > Nov 17 14:25:14 dave dovecot: lmtp: Error: > /usr/local/lib/ruby/gems/2.3.0/gems/sqlite3-1.3.12/lib/sqlite3/pragmas.rb:107: > warning: previous definition of integrity_check was here > > Nov 17 14:25:14 dave logstats[29232]: Error: unrecognized auto_vacuum true > > > The 'integrity_check' method is indeed re-defined. There's no line > number/filename wrt the 'auto_vacuum' problem. > > Anyone know how to fix this? Thanks in advance... > > Steve Witten > > > > > -- > You received this message because you are subscribed to the Google Groups > "sqlite3-ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "sqlite3-ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
