Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Even though it was from a while, this bug report seems to be what you are having an issue with: <a href="http://bugs.mysql.com/bug.php?id=4541" rel="nofollow noreferrer">http://bugs.mysql.com/bug.php?id=4541</a></p> <p>You may want to read through the comments on this bug, and see if they are referring to your situation, since it is hard to help without seeing what command you used to get this error, nor knowing which version of mysql.</p> <p>UPDATE: Based on your query, you may want to remove this first:</p> <pre><code>INDEX ( `feed_id` , `guid` , `publish_date` , `update_of` , `title` ) </code></pre> <p>Then, try doing:</p> <pre><code>INDEX ( `feed_id`) </code></pre> <p>When I see a long index like this I get suspicious.</p> <p>Ideally you should index what you will be doing selects on, so unless you have </p> <pre><code>SELECT * FROM table WHERE feed_id=? AND guid=? AND publish_date=? AND update_of=? and title=? </code></pre> <p>then this index is useless. Since feed_id is a primary key you should just do</p> <pre><code>SELECT * FROM table where feed_id=? </code></pre> <p>as it will uniquely return one row.</p> <p>So the index I have above would be what is needed. You may also want a separate index on title and perhaps publish_date. </p> <p>Look at what queries you are writing, then you can determine where indexes should be. Indexes will get expensive as you add more rows, so you don't want to index too much, but indexing too little is useless, so that is why I suggest you look at the queries then decide where to have indexes.</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.
 

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