libdb/examples/c
2012-11-14 16:35:20 -05:00
..
csv Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_apprec Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_rep Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_rep_chan Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_rep_gsg Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
getting_started Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
txn_guide Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_access.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_btrec.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_bulk.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_env.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_heap.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_lock.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_mpool.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_sequence.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_stream.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_thread.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
ex_tpcb.c Release 5.3.21 5/11/2012 2012-11-14 16:35:20 -05:00
README Release 5.2.28 on 6/10/2011 2011-09-13 13:44:24 -04:00

# $Id$

getting_started/
		Examples from the Getting Started Guide

ex_access.c	Using just the DB access methods.

ex_apprec/	Application-specific recovery.

ex_btrec.c	Using the BTREE access method with record numbers.

ex_bulk.c	Bulk interfaces.

ex_dbclient.c	Using DB from an RPC client.

ex_env.c	Setting up the DB environment.

ex_lock.c	Locking.

ex_mpool.c	Shared memory buffer pools.

ex_rep/		Replication.  This creates a toy stock quote server
		with DB's single-master, multiple-client replication,
		with communication over TCP.  See ex_rep/README.

ex_sequence.c	Sequences.

ex_thread.c	Threaded application with multiple readers and writers.

ex_tpcb.c	TPC/B.
		Ex_tpcb sets up a framework in which to run a TPC/B test.
		Database initialization (the -i flag) and running the
		benchmark (-n flag) must take place separately (i.e.,
		first create the database, then run 1 or more copies of
		the benchmark).  Furthermore, when running more than one
		TPCB process, it is necessary to run the deadlock detector
		(db_deadlock), since it is possible for concurrent tpcb
		processes to deadlock.  For performance measurement, it
		will also be beneficial to run the db_checkpoint process
		as well.