Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>the relevant 2 lines:</p> <p><a href="https://github.com/ernie/meta_search/blob/master/lib/meta_search.rb#L55" rel="nofollow">https://github.com/ernie/meta_search/blob/master/lib/meta_search.rb#L55</a></p> <p><a href="https://github.com/ernie/meta_search/blob/master/lib/meta_search/searches/active_record.rb#L46" rel="nofollow">https://github.com/ernie/meta_search/blob/master/lib/meta_search/searches/active_record.rb#L46</a></p> <p>I don't think it is a bug, it is just how things are. </p> <p>in scenario 3 In development environment, you do not preload the model. When you require 'meta_search', it will define 'search' on <code>ActiveRecord::Base</code>. Then you say <code>Document</code>, which loads the model, will first inherit defined search method so when it includes Tire search module, it will leave search aliased to metasearch.</p> <p>In production mode (scenario 4) as well as scenario 2, you preload the document model before metasearch so Tire will define search. Now requiring metasearch will only have effect on newly loaded classes.</p> <p>You can see that the order in which gems are defined does not count. But you can undefine search method after gem require.</p> <pre><code># application.rb # ... Bundler.require(:default, Rails.env) if defined?(Bundler) # now move search out of the way ActiveRecord::Base.instance_eval { undef :search } </code></pre> <p>so any time later we load a model class and include tire, search will correctly go to tire, both in development and production.</p> <p>This is not ideal since the search method for non-tire models will not delegate to metasearch, in fact it will not be defined. So probably the second solution is best: here you overwrite the search method with one which checks for tire at runtime:</p> <pre><code>class ActiveRecord::Base def self.search(*args, &amp;block) if respond_to?(:tire) tire.search(*args, &amp;block) else metasearch(*args, &amp;block) end end end </code></pre> <p>does this help?</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I stop meta_search from defining search on my models?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USViktor Trón
    1. USViktor Trón
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I stop meta_search from defining search on my models?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for the answer and for explaining what is going on :) - I've tried to implement the first suggestion, since I don't ever want search to be aliased to metasearch (only thing which uses it is active_admin) - but I'm getting an error: `application.rb:11:in `remove_method': method `search' not defined in Class (NameError).` If I remove that and try it in the console: `1.9.3p125 :004 > ActiveRecord::Base.methods.include? :search #=> true 1.9.3p125 :005 > ActiveRecord::Base.send(:remove_method, :search) NameError: method `search' not defined in ActiveRecord::Base`
      singulars
      1. PO
      1. USJords
    2. COyou are trying to remove the instance method, we need the class method. Look my << in the response, crucial.
      singulars
      1. PO
      1. USViktor Trón
    3. COyou could try ActiveRecord::Base.instance_eval { undef :search } instead
      singulars
      1. PO
      1. USViktor Trón
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload