xapian_db 1.3.7 → 1.3.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8fcb96848f64b5fb55dee7fcd4cd2fa246c3161b
-  data.tar.gz: d084663854eccb8578c0cc6f8c91244034a51f37
+  metadata.gz: f5b58a771fe0958c2b5058fed842f532d02d83d2
+  data.tar.gz: cf1801e0f6d3386031084d274073bc75572af6a1
 SHA512:
-  metadata.gz: 9887f97d274399336ff92f7ee41d9b6d9a89df483a355b28673891bd4c96acc8541548e5dc95e2cd15e90739fc72480d6bbedf1dad96de488f0a4cc12424ac44
-  data.tar.gz: 86a87a39b867e19bf1ba8115b94657ea924628c0a62c670bd4cc68069b590196c7414dd471e1b76937ebf4debc463c7361b67af6b1adb99bd64a8edf95dd4fb7
+  metadata.gz: 6c73a5ccda203e1242cea1aedb58e1e738f4fc599c89e2a2b7f37e77acb938392726164a5c6f4580595452a3fafa37faa466c07ba46d4f80461142f39fcb2656
+  data.tar.gz: 22483ae031a7f96cc7ea13cf67b109699db418fef80d980b662b9339109384fe67961f2f82201d5d1de25cee34b292c3c11a32bb3f5f160cb9f096c85514e8d6

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+##1.3.7.1 (March 3rd, 2018)
+
+Changes:
+
+  - Allow access to configured blueprints through XapianDb::DocumentBlueprint
+
 ##1.3.7 (January 12th, 2016)
 
 Breaking Changes:

data/README.rdoc

@@ -47,7 +47,7 @@ Make sure version 1.2.6 or newer is installed.
 If you want to use xapian_db in a Rails app, you need Rails 3 or newer.
 
 For a first look, look at the examples in the examples folder. There's the simple ruby script basic.rb that shows the basic
-usage of XapianDB without rails. In the basic_rails folder you'll find a very simple Rails app unsing XapianDb.
+usage of XapianDB without rails. In the basic_rails folder you'll find a very simple Rails app using XapianDb.
 
 The following steps assume that you are using xapian_db within a Rails app.
 
@@ -64,7 +64,7 @@ You can override these defaults by placing a config file named 'xapian_db.yml' i
     adapter: datamapper # Avaliable adapters: :active_record, :datamapper
     language: de        # Global language; can be overridden for specific blueprints
     term_min_length: 2  # Ignore single character terms
-    enable_query_flags: FLAG_PHRASE, FLAG_SPELLING_CORRECTION
+    enabled_query_flags: FLAG_PHRASE, FLAG_SPELLING_CORRECTION
 
   development:
     database: db/xapian_db/development
@@ -205,7 +205,7 @@ by their accentless form:
   end
 
   XapianDb::Config.setup do |config|
-    config.indexer_preprocess_callback UtilT.method(:strip_accents)
+    config.indexer_preprocess_callback Util.method(:strip_accents)
   end
 
 You may use attributes from associated objects in a blueprint; if you do that and an associated object is updated, your objects should be reindexed, too. You can tell XapnaDB about those dependencies like so:

data/lib/xapian_db/document_blueprint.rb

@@ -26,6 +26,8 @@ module XapianDb
     # ---------------------------------------------------------------------------------
     class << self
 
+      attr_reader :blueprints
+
       # Configure the blueprint for a class.
       # Available options:
       # - adapter (see {#adapter} for details)

data/lib/xapian_db/query_parser.rb

@@ -35,6 +35,10 @@ module XapianDb
 
       # Add the searchable prefixes to allow searches by field
       # (like "name:Kogler")
+      processors = [] # The reason for having a seemingly useless "processors" array is as follows:
+      # We need to add a reference to the generated Xapian::XYValueRangeProcessor objects to the scope that calls parser.parse_query.
+      # If we don't, the Ruby GC will often garbage collect the generated objects before parser.parse_query can be called,
+      # which would free the memory of the corresponding C++ objects and result in segmentation faults upon calling parse_query.
       XapianDb::DocumentBlueprint.searchable_prefixes.each do |prefix|
         parser.add_prefix(prefix.to_s.downcase, "X#{prefix.to_s.upcase}")
         type_info = XapianDb::DocumentBlueprint.type_info_for(prefix)
@@ -42,11 +46,17 @@ module XapianDb
         value_number = XapianDb::DocumentBlueprint.value_number_for(prefix)
         case type_info
           when :date
-            parser.add_valuerangeprocessor Xapian::DateValueRangeProcessor.new(value_number, "#{prefix}:")
+            processor = Xapian::DateValueRangeProcessor.new(value_number, "#{prefix}:")
+            processors << processor
+            parser.add_valuerangeprocessor(processor)
           when :number
-            parser.add_valuerangeprocessor Xapian::NumberValueRangeProcessor.new(value_number, "#{prefix}:")
+            processor = Xapian::NumberValueRangeProcessor.new(value_number, "#{prefix}:")
+            processors << processor
+            parser.add_valuerangeprocessor(processor)
           when :string
-            parser.add_valuerangeprocessor Xapian::StringValueRangeProcessor.new(value_number, "#{prefix}:")
+            processor = Xapian::StringValueRangeProcessor.new(value_number, "#{prefix}:")
+            processors << processor
+            parser.add_valuerangeprocessor(processor)
         end
       end
       query = parser.parse_query(expression, @query_flags)

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: xapian_db
 version: !ruby/object:Gem::Version
-  version: 1.3.7
+  version: 1.3.7.1
 platform: ruby
 authors:
 - Gernot Kogler
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-01-12 00:00:00.000000000 Z
+date: 2018-03-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: daemons
@@ -261,7 +261,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: Ruby library to use a Xapian db as a key/value store with high performance