View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003933 | MMW v4 | DB/FileMonitor | public | 2007-11-09 11:53 | 2007-11-13 22:38 |
| Reporter | jiri | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003933: Improve some SQL queries | ||||
| Description | One user pointed out that some queries could be improved. By his own words: Oh and another thing, I noticed that the SQL used to populate the main window when browsing various nodes aren't consistent/tuned properly. E.g. adding song from a genre node uses this sql: SELECT Songs.* FROM Songs WHERE exists (SELECT NULL FROM GenresSongs WHERE GenresSongs.IDSong=Songs.ID AND GenresSongs.IDGenre=?) When this is at least ten times faster: SELECT Songs.* FROM Songs WHERE ID IN (SELECT IDSong FROM GenresSongs WHERE GenresSongs.IDGenre=?) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1100 | ||||
|
|
We could change this and make sure there aren't any such suboptimal queries. |
|
|
It is true. It is at least ten times faster: So I fixed it across the product for GenresSongs, ArtistsSongs, ListSongs, PodcastEpisodes tables in order to be faster. i.e. Queries which consists of these tables are much faster now + the original query for adding songs from a genre node is much faster now. Fixed in build 1100. |
|
|
Verified no regressions in 1104. |
