blob: 1515ac092561b3e5db3783c709c97ecfcabfa255 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*-
* vim: sw=2 ts=2 et lcs=trail\:.,tab\:>~ :
* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
#include "nsISupports.idl"
interface mozIStorageAsyncConnection;
/**
* This interface contains the information that the Storage service needs to
* vacuum a database. This interface is created as a service through the
* category manager with the category "vacuum-participant".
* Please see https://developer.mozilla.org/en/mozIStorageVacuumParticipant for
* more information.
*/
[scriptable, uuid(8f367508-1d9a-4d3f-be0c-ac11b6dd7dbf)]
interface mozIStorageVacuumParticipant : nsISupports {
/**
* The expected page size in bytes for the database. The vacuum manager will
* try to correct the page size by executing a full vacuum.
*
* @note If the database is using the WAL journal mode, the page size won't
* be changed to the requested value. See bug 634374.
* @note Valid page size values are powers of 2 between 512 and 65536.
* The suggested value is mozIStorageConnection::defaultPageSize.
*/
readonly attribute long expectedDatabasePageSize;
/**
* Whether the main schema should be using auto_vacuum = INCREMENTAL.
* This will cause auto_vacuum to change to INCREMENTAL if it's not set yet.
* It is not possible to change mode of any attached databases through this,
* to do that you must open a separate connection and use asyncVacuum() on it.
*/
readonly attribute boolean useIncrementalVacuum;
/**
* Connection to the database file to be vacuumed.
*/
readonly attribute mozIStorageAsyncConnection databaseConnection;
/**
* Notifies when a vacuum operation begins. Listeners should avoid using the
* database till onEndVacuum is received.
*
* @return true to proceed with the vacuum, false if the participant wants to
* opt-out for now, it will be retried later. Useful when participant
* is running some other heavy operation that can't be interrupted.
*
* @note When a vacuum operation starts or ends it will also dispatch global
* "vacuum-begin" and "vacuum-end" notifications through the observer
* service with the data argument being the database filename.
*/
boolean onBeginVacuum();
/**
* Notifies when a vacuum operation ends.
*
* @param aSucceeded
* reports if the vacuum succeeded or failed.
*/
void onEndVacuum(in boolean aSucceeded);
};
|
