69b874fee0
The methodology used to generate this CL is documented in https://crbug.com/1098010#c95. No-Try: true Bug: 1098010 Change-Id: I68bb81a4dcae37f944f4d8cd39d82ed540364615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3899461 Reviewed-by: Mark Mentovai <mark@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org> Auto-Submit: Avi Drissman <avi@chromium.org> Owners-Override: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1047607}
28 lines
1.1 KiB
C++
28 lines
1.1 KiB
C++
// Copyright 2019 The Chromium Authors
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
#ifndef SQL_VFS_WRAPPER_FUCHSIA_H_
|
|
#define SQL_VFS_WRAPPER_FUCHSIA_H_
|
|
|
|
#include "third_party/sqlite/sqlite3.h"
|
|
|
|
namespace sql {
|
|
|
|
// Fuchsia doesn't provide a file locking mechanism like flock(). These
|
|
// functions are used to simulate file locking. On Fuchsia profile directories
|
|
// are not expected to be shared with other processes and therefore only one
|
|
// browser process may access sqlite files. These functions are designed to
|
|
// handle the case when the same sqlite database is open more than once from the
|
|
// same browser process. In most cases databases do not need to be open more
|
|
// than once, i.e. contention is expected to be rare, so the main goal of the
|
|
// design is simplicity and not performance. The manager maintains a list of all
|
|
// currently locked files.
|
|
int Lock(sqlite3_file* sqlite_file, int file_lock);
|
|
int Unlock(sqlite3_file* sqlite_file, int file_lock);
|
|
int CheckReservedLock(sqlite3_file* sqlite_file, int* result);
|
|
|
|
} // namespace sql
|
|
|
|
#endif // SQL_VFS_WRAPPER_FUCHSIA_H_
|