Google Git
Sign in
chromium / chromium / src / 0164fe22baf9c69a18152fcdc99cb15e6124def2 / . / components / test / data / history
tree: aa8528e45fe85796cde9f1baeaab148709a73556 [path history] [tgz]
  1. thumbnail_wild/
  2. Favicons.v3.sql
  3. Favicons.v4.sql
  4. Favicons.v5.sql
  5. Favicons.v6.sql
  6. Favicons.v7.sql
  7. Favicons.v8.sql
  8. history.22.sql
  9. history.26.sql
  10. history.27.sql
  11. history.28.sql
  12. history.29.sql
  13. history.30.sql
  14. history.31.sql
  15. history.32.sql
  16. history.38.sql
  17. history.39.sql
  18. history.40.sql
  19. history.41.sql
  20. history.42.sql
  21. history.43.sql
  22. history.44.sql
  23. history.45.sql
  24. history.46.sql
  25. history.47.sql
  26. history.48.sql
  27. history.49.sql
  28. history.50.sql
  29. history.52.sql
  30. history.53.sql
  31. history.54.sql
  32. history.55.sql
  33. history.56.sql
  34. history.57.sql
  35. history.58.sql
  36. history.59.sql
  37. history.60.sql
  38. history.61.sql
  39. history.62.sql
  40. History_with_starred
  41. HistoryNoDuration
  42. HistoryNoSource
  43. OWNERS
  44. README.md
  45. TopSites.v1.sql
  46. TopSites.v2.sql
  47. TopSites.v3.sql
  48. TopSites.v4.sql
  49. TopSites.v5.sql
components/test/data/history/README.md

How to generate history.N.sql files using a Chromium build.

On a Linux build:

  1. Build the sqlite_shell target. This will build the SQLite CLI.

     $ ninja -C out/Debug/ sqlite_shell

  2. Run Chrome/Chromium with a fresh profile directory and immediately quit. It doesn‘t really matter how long you run it, but there’ll be less work for you if you quit early.

     $ out/Debug/chrome-wrapper --user-data-dir=foo

  3. Locate the History file in the user-data-dir directory; e.g., foo/Default/History.

  4. Dump the History database into a text file:

     $ echo '.dump' | out/Debug/sqlite_shell foo/Default/History > history.sql

  5. Manually remove all INSERT INTO statements other than the statements populating the meta table.

To generate history.N.sql, be sure to run these steps before implementing the N+1 migration in chromium. I.e. you'll usually want to run these steps on the main branch rather than the CL branch.