Revert "HistoryDatabase: improve migration code."

This reverts commit bf26f69d67dae2edda3d7cb9e49f1657ebbf2cc1.

Reason for revert: cause a large regression on profile loading on startup
  see: https://uma.googleplex.com/p/chrome/timeline_v2?sid=882662815ae5ed662333e03bed4409d8

Bug: 409355667, 40891923
Original change's description:
> HistoryDatabase: improve migration code.
>
> 1. Delete old migration code. Chromium generally doesn't support
> forward-migrating data that is more than 2 years old. This change
> deletes migration code that has been live for at least two years. This
> reduces binary bloat (-17kB on Android arm32) and removes some migration
> anti-patterns, which hopefully will help prevent future code being added
> that uses these patterns. See crbug.com/409355667
>
> 2. Use compatible version correctly. This value is meant to represent
> the oldest version of Chromium *code* that can use the current version
> of Chromium *data*, i.e. support for downgrades. Chromium generally
> doesn't attempt to support downgrading, but the migrations to v69 and
> v70 were backwards compatible, so code for 68 should be fine to run with
> data from 69+. This value was not actually being set at all previously.
>
> 3. Handle failure to update meta table.
>
> Bug: 409355667, 40891923
> Change-Id: I9901f1d5117e726c116575d742229c6201e70303
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6442189
> Reviewed-by: Etienne Bergeron <etienneb@chromium.org>
> Reviewed-by: manuk hovanesian <manukh@chromium.org>
> Commit-Queue: Evan Stade <evanstade@microsoft.com>
> Cr-Commit-Position: refs/heads/main@{#1447350}

Bug: 409355667, 40891923
Change-Id: I2bdb4df7649cd93fcd88594d9844f82afc69a007
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6681148
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: manuk hovanesian <manukh@chromium.org>
Reviewed-by: Evan Stade <evanstade@microsoft.com>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1479848}
51 files changed
tree: fbf51498863b69385df504c720b6584863c47d00
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.