Db.sync
Db.sync |
|
import com.sleepycat.db.*;public int sync(int flags) throws DbException;
The Db.sync method flushes any cached information to disk.
If the database is in memory only, the Db.sync method has no effect and will always succeed.
The flags parameter is currently unused, and must be set to 0.
It is important to understand that flushing cached information to disk only minimizes the window of opportunity for corrupted data. Although unlikely, it is possible for database corruption to happen if a system or application crash occurs while writing data to the database. To ensure that database corruption never occurs, applications must either: use transactions and logging with automatic recovery; use logging and application-specific recovery; or edit a copy of the database, and once all applications using the database have successfully called Db.close, atomically replace the original database with the updated copy.
The Db.sync method throws an exception that encapsulates a non-zero error value on failure, and returns Db.DB_INCOMPLETE if the underlying database still has dirty pages in the cache. (The only reason to return Db.DB_INCOMPLETE is if another thread of control was writing pages in the underlying database file at the same time as the Db.sync method was being called. For this reason, a return of Db.DB_INCOMPLETE can normally be ignored; or, in cases where it is a possible return value, there may be no reason to call Db.sync.)
The Db.sync method may fail and throw an exception encapsulating a non-zero error for the following conditions:
The Db.sync method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the Db.sync method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
d17 1
a17 1
d25 1
a25 1
throws DbException;
d102 1
a102 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d24 1
a24 1
public void sync(int flags)
d43 8
a50 1
failure.
d57 3
a59 3
If a catastrophic error has occurred, the Db.sync method may fail and
throw a DbRunRecoveryException,
in which case all subsequent Berkeley DB calls will fail in the same way.
d63 37
a99 1
Databases and Related Methods
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 2
a2 2
d4 1
d25 1
a25 1
public int sync(int flags)
d44 1
a44 8
failure, and returns Db.DB_INCOMPLETE if the underlying database still has
dirty pages in the cache. (The only reason to return
Db.DB_INCOMPLETE is if another thread of control was writing pages
in the underlying database file at the same time as the
Db.sync method was being called. For this reason, a return of
Db.DB_INCOMPLETE can normally be ignored; or, in cases where it is
a possible return value, there may be no reason to call
Db.sync.)
d51 3
a53 3
If a catastrophic error has occurred, the Db.sync method may fail and throw
a DbRunRecoveryException, in which case all subsequent Berkeley DB calls
will fail in the same way.
d57 1
a57 37
Db.associate,
Db.close,
Db.cursor,
Db.del,
Db.fd,
Db.get,
Db.pget,
Db.get_byteswapped,
Db.get_type,
Db.join,
Db.key_range,
Db.open,
Db.put,
Db.remove,
Db.rename,
Db.set_append_recno,
Db.set_bt_minkey,
Db.set_cachesize,
Db.set_errcall,
Db.set_errpfx,
Db.set_feedback,
Db.set_flags,
Db.set_h_ffactor,
Db.set_h_nelem,
Db.set_lorder,
Db.set_pagesize,
Db.set_q_extentsize,
Db.set_re_delim,
Db.set_re_len,
Db.set_re_pad,
Db.set_re_source,
Db.stat,
Db.sync,
Db.truncate,
Db.upgrade,
and
Db.verify.
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d1 2
a2 2
a3 1
d24 1
a24 1
public void sync(int flags)
d43 8
a50 1
failure.
d57 3
a59 3
If a catastrophic error has occurred, the Db.sync method may fail and
throw a DbRunRecoveryException,
in which case all subsequent Berkeley DB calls will fail in the same way.
d63 37
a99 1
Databases and Related Methods
@