d343478be1
After https://crrev.com/c/5248489, Chromium parses "id" and "match-dest" option of "Use-As-Ditionary" response header. But those information is not stored in the SQL database. This CL adds the support. To store the information, the SQL database needs to be updated as following: - Change the existing `id` field to `primary_key`. - Add a new `id` field to store the "id" option. - Add a new `match_dest` field to store the "match-dest" option. - Add the `match_dest` to the `unique_index` index. - Change kCurrentVersionNumber and kCompatibleVersionNumber from 1 to 2. As the existing database scheme (version 1) is used only for the first Origin Trial (M119-M122), we don't need to migrate the data from version 1 to the new scheme (version 2). So `DoMigrateDatabaseSchema()` method just deletes the existing table `dictionaries` and the `total_dict_size` metadata. Bug: 1413922 Change-Id: Ia2841e4f022cc48cf766b51639cd7047f6a1bc81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5271881 Reviewed-by: Patrick Meenan <pmeenan@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1257129}
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.