bffef51ac1
The database option `exclusive_locking` is enabled by default. NOTE: This CL has no functional changes. It was used to be recommended to explicitly specify it to avoid using the default DatabaseOptions constructor which had `exclusive_locking` to false (due historical reason related to unittests migration). The following CL [landed] fixes the default constructor and by default all database as using the `exclusive_locking` mode. see: https://chromium-review.googlesource.com/c/chromium/src/+/5029223 The recommendation from now is to explicitly specify the non exclusive case with an explanation of why the database can be accessed in that mode. Bug: 1120969 Change-Id: Ib278d967c76c1ea8494ebaa4bb1723f0fb74c30e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5251553 Reviewed-by: Maks Orlovich <morlovich@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/main@{#1256381}