Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'll assume you have the latest version of sunspot gem.</p> <ol> <li><p>Sunspot reindexes each time the model has changed. To tweak this behaviour (see <a href="https://github.com/outoftime/sunspot_rails/wiki/Installation-and-configuration" rel="nofollow noreferrer">options for searchable</a>):</p> <p>searchable :ignore_attribute_changes_of => [ :average_rating, :permalink ] do text :title end</p> <p>Take a look on the source code: <a href="https://github.com/outoftime/sunspot/blob/master/sunspot_rails/lib/sunspot/rails/searchable.rb#L393" rel="nofollow noreferrer">https://github.com/outoftime/sunspot/blob/master/sunspot_rails/lib/sunspot/rails/searchable.rb</a></p></li> <li><p>Your site should still work until the first request to solr:</p> <ul> <li><p>either a full text search request</p></li> <li><p>either an indexing request</p></li> </ul> <p>You are probably making an update on the user model each time a user logs in, therefore triggering a reindex.</p></li> </ol> <p>More tips:</p> <ul> <li><p>in fact, it's not the indexing that takes a lot of time, it's the commit command; the commit command is issued, by default, on the end of each web request ; This is very costly in a production env. I advice you to <a href="https://stackoverflow.com/questions/4937314/setup-sunspot-solr-with-rails-in-production-environment">change the policy</a> to <a href="http://wiki.apache.org/solr/SolrConfigXml#Update_Handler_Section" rel="nofollow noreferrer">autocommit after X seconds</a>; </p></li> <li><p>if you want that your want to patch sunspot so that you site should work in case of solr server failure, I advise you to take a look on this gem, that mocks server interface for the test env: <a href="https://github.com/pivotal/sunspot_matchers" rel="nofollow noreferrer">sunspot_matchers</a></p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POSunspot Index Only When Searchable Fields Change
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVlad Zloteanu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSunspot Index Only When Searchable Fields Change
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWill resort to ignore_attributes of. Kind of annoying to have to specify this when we explicitly declare searchable fields. Do you forsee any complications if I were to create a patch which adds additional logic to the searchable.rb to query the sunspot setup to determine if the changed fields will affect the index?
      singulars
      1. PO
      1. USghempton
 

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