Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>No this wont work. It because of the 'artitecture' of sphinxSE/mysql. </p> <p>Sphinx of course doesnt present real tables to mysql. It pretends its a table. It tells the mysql query optimiser works very well via indexes. So the optimizer should always pick the SphinxSE table 'first', which is then joined with the real mysql table. </p> <p>So for each row, it does an index scan on the SphinxSE table, which gets the doc_ids. and it then looks them up in the origial table (the join itself). </p> <p>SphinxSE cant exist on the 'right' side of a Join. Always must be first (or left). </p> <p>... your query (using left join) is forcing mysql to put the sphinxSE table (well tables no less!) on the right, which simply wont work. </p> <hr> <p>You need to reform the query as a single sphinxSE table. A sphinxSE table can search multiple sphinx indexes at once. Or can maybe reform your actual indexes to make once index.</p> <p>Remember can be multiple fields per index - so an <strong>extended</strong> query could perhaps be used</p> <p>(@field1 "some random name") | (@field2 "some random name") </p> <p>... result one sphinxSE table (on the left of the join :) ). </p> <hr> <p>Updated to add: </p> <p>Creating a sphinxSE to search two indexes at once (like a sql UNION) pretty sure you can do</p> <pre><code>CREATE TABLE ... CONNECTION="sphinx://localhost:9312/index1,index2"; </code></pre> <p>but even if you cant, overriding it at query time should definitely work, example from the docs:</p> <pre><code>... WHERE query='test;index=test1,test2,test3;'; </code></pre> <p>The index defined in the table will be ignored, so can use any sphinxSE table. </p>
    singulars
    1. This table or related slice is empty.
    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. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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