Hi all! I have a db looking like this: http://onnerby.se/~daniel/mc2db.png and in my tracks table I have a column named sort_order1. When my application is running I try to optimize the database by doing a pretty massive SELECT to set this sort_order looking like this: SELECT t.id FROM tracks t LEFT OUTER JOIN genres g ON t.visual_genre_id=g.id LEFT OUTER JOIN albums al ON t.album_id=al.id LEFT OUTER JOIN artists ar ON t.visual_artist_id=ar.id LEFT OUTER JOIN folders f ON t.folder_id=f.id ORDER BY g.sort_order,ar.sort_order,al.sort_order,t.track,f.fullpath,t.filename
This works great but when I upgraded from 3.5.7 to 3.5.8 the speed of this select went from 0.2s to around 1 minute. And 3.5.8 is stealing ALOT more memory. I tried this both in my own application and using the sqlite.exe (both for 3.5.7 and 3.5.8) and they show the same results. I tried to locate anything regarding this both on the mailinglist and searching tickets. Is this a known issue or is it a bug? Best regards Daniel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
