Confirmed users
595
edits
User talk:Mak77: Difference between revisions
→Places Database Splitting
| Line 33: | Line 33: | ||
Ideally we could hold both keys, since adding an url column with an index will increase the table size, we could continue joining on "place_id" inside history.sqlite, while using "url" inside bookmarks.sqlite. | Ideally we could hold both keys, since adding an url column with an index will increase the table size, we could continue joining on "place_id" inside history.sqlite, while using "url" inside bookmarks.sqlite. | ||
Actually this change would also make bookmarks/keywords/tags checks against | Actually this change would also make bookmarks/keywords/tags checks against an url much faster since we would not need anymore to join with moz_places (url would be also inside moz_bookmarks) | ||
The migration patch would allow us to regenerate all tables, fixing bogus column names and adding other columns we need from some time like last_visit and referer. Also regenerating dbs would make a VACUUM, that is surely a nice thing to do at this time. | The migration patch would allow us to regenerate all tables, fixing bogus column names and adding other columns we need from some time like last_visit and referer. Also regenerating dbs would make a VACUUM, that is surely a nice thing to do at this time. | ||