Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In addition to what has been said, when in a clustered environment:</p> <p><strong>Hibernate-search:</strong></p> <p>Cons:</p> <ul> <li>Requires a master/slave combination which isn't always feasible, specially when your build/deployment process doesn't distinguish among the nodes (same war for all nodes).</li> <li>The indexes are hosted in the same server/process as the application running Hibernate, so you have one index per application node. This is sometimes overkill.</li> <li>It isn't real-time search, unless the load balancer uses session stickiness.</li> </ul> <p>Pros:</p> <ul> <li>Zero to little configuration. Just drop the jar in the classpath.</li> <li>The bridge between Hibernate and Lucene is very straight forward. Just annotate the Entities and voilá!</li> </ul> <p><strong>Solr/SolrCloud:</strong></p> <ul> <li>It is decoupled of the application it self. </li> <li>Not real-time search, just as hibernate-search.</li> <li>Requires restart to change the schema.</li> <li>SolrCloud isn't exactly the easiest framework to configure.</li> <li>No straight forward Hibernate bridge. You have to code your own Hibernate listener and bind them to post-[insert|delete|update] events (or find an open source one) </li> </ul> <p><strong>ElasticSearch</strong></p> <ul> <li>Servers are independent of the application, just like solr.</li> <li>It is by far the easiest to configure in a cluster/cloud.</li> <li>It is <strong>real-time</strong></li> <li>No straight forward Hibernate bridge, as well. (es-hibernate-connector on GitHub)</li> </ul> <p>Personally I prefer ElasticSearch when running in the cloud.</p>
    singulars
    1. This table or related slice is empty.
    1. POSolr vs Hibernate Search - Which to choose and When?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScarlspring
    1. USFranklin Dattein
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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