StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSlow SQL Query on indexed columns, multi-column number
primarykey
Id
11909695
data
AcceptedAnswerId
11958249
AnswerCount
3
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-08-10T21:46:18.223
FavoriteCount
0
LastActivityDate
2012-08-14T18:12:10.577
LastEditDate
2012-08-14T15:33:44.337
LastEditorUserId
782868
OwnerUserId
782868
ParentId
0
PostTypeId
1
Score
1
ViewCount
615
LastEditorDisplayName
text
Body
I have a table that is comprised of 6 numbers as the primary key <pre><code>CREATE TABLE table1 ( num1 decimal, num2 int, num3 int, num4 bigint, num5 bigint, num6 bigint, PRIMARY KEY (num1, num2, num3, num4, num5, num6)) </code></pre> I need to access the table in sorted order and often times I have a need to query the table to find the next N large numbers in order and their associated data. So the query I wrote was something like this <pre><code>SELECT * FROM table1 WHERE num1 >? OR ( (num1 == ? AND num2 > ?) OR ( (num1 == ? AND num2 == ? AND num3 > ?) OR ( (num1 == ? AND num2 == ? AND num3 == ? AND num4 > ? OR ( (num1 == ? AND num2 == ? AND num3 == ? AND num4 == ? AND num5 > ?) OR ( (num1 == ? AND num2 == ? AND num3 == ? AND num4 == ? AND num5 == ? AND num6 > ?)))))) ORDER BY num1, num2, num3, num4, num5, num6 LIMIT ?; </code></pre> This was the best way I could see to find the next largest key, and this does query in the order of the index however....query takes a few seconds, which is something that I'm not to fond of. Is there any way to improve the performance? This takes a few seconds to execute on a table of 10million rows and I need it to execute more on the order of 100ms. Query Plan: <pre><code>"SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1>?) (~250000 rows)" "SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1=? AND num2>?) (~2 rows)" "SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1=? AND num2=? AND num3>?) (~2 rows)" "SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1=? AND num2=? AND num3=? AND num4>?) (~2 rows)" "SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1=? AND num2=? AND num3=? AND num4=? AND num5>?) (~1 rows)" "SEARCH TABLE table1 USING INDEX sqlite_autoindex_table1_1 (num1=? AND num2=? AND num3=? AND num4=? AND num5=? AND num6>?) (~1 rows)" "USE TEMP B-TREE FOR ORDER BY" </code></pre> Edit: Why is this not possible? I literally want to get things in the INDEXED ORDER, the same order generated by the <code>ORDER BY</code> keyword?
Tags
<sql><performance><sqlite><indexing><query-optimization>
Title
Slow SQL Query on indexed columns, multi-column number
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJohn Lotacs
UserOwnerUserId
1. USJohn Lotacs
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POSlow SQL Query on indexed columns, multi-column number
 UserUserId
 USJohn Lotacs
 VoteTypeVoteTypeId
 VTBountyStart
2. VO
 singulars
 PostPostId
 POSlow SQL Query on indexed columns, multi-column number
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.