sqlite - Performance Tuning

Not logged in

• Honeypot
• Browse
• Home
• Login
• Reports
• Search
• Ticket
• Timeline
• Wiki

• Contents
• No-Diff
• Text

*** 11,16 ****
  <i><b>SQLite implements JOIN USING by translating the USING clausing into some extra WHERE clause terms.  It does the same with NATURAL JOIN and JOIN ON. So while those constructs might be helpful to the human reader, they don't really make any difference to SQLite's query optimizer.</b></i><br>
  So if there work in working out joins it stands to reason that doing that work for SQLITE will speed up the compile times.  If you are returning 100's of rows this might not mater but if you are returning 1 row many times this might be a big issue.
  
! 
  
  </html>
--- 11,17 ----
  <i><b>SQLite implements JOIN USING by translating the USING clausing into some extra WHERE clause terms.  It does the same with NATURAL JOIN and JOIN ON. So while those constructs might be helpful to the human reader, they don't really make any difference to SQLite's query optimizer.</b></i><br>
  So if there work in working out joins it stands to reason that doing that work for SQLITE will speed up the compile times.  If you are returning 100's of rows this might not mater but if you are returning 1 row many times this might be a big issue.
  
! <H2>Order your tables properly in your where clause</H2>
! Place the tables where you can eliminate the most rows from using a where clause (preferably on an indexed column) first, in order to limit the number of join operations required.  
  
  </html>