chronicle). A client gets one or more Database objects using {@link DatabaseFactory}. Five interfaces play an important role in the data model underlying CrNiCKL:
edit() method. Two methods are provided for transactions management: {@link #commit()} and {@link #rollback()}. These methods are not used internally by CrNiCKL. Managing transactions and implementing transaction boundaries is the client's responsibility. @author Jean-Paul Vetterli @version 1.0.0
The following features are supported:
Database attributes are specified in the {@link com.sleepycat.db.DatabaseConfig DatabaseConfig} class.
Database handles are free-threaded unless opened in an environment that is not free-threaded.
To open an existing database with default attributes:
To create a transactional database that supports duplicates:Environment env = new Environment(home, null); Database myDatabase = env.openDatabase(null, "mydatabase", null);
DatabaseConfig dbConfig = new DatabaseConfig(); dbConfig.setTransactional(true); dbConfig.setAllowCreate(true); dbConfig.setSortedDuplicates(true); Database newlyCreateDb = env.openDatabase(txn, "mydatabase", dbConfig);
Database attributes are specified in the {@link com.sleepycat.je.DatabaseConfig DatabaseConfig} class. Database handles arefree-threaded and may be used concurrently by multiple threads.
To open an existing database with default attributes:
Environment env = new Environment(home, null); Database myDatabase = env.openDatabase(null, "mydatabase", null);
To create a transactional database that supports duplicates:
DatabaseConfig dbConfig = new DatabaseConfig(); dbConfig.setTransactional(true); dbConfig.setAllowCreate(true); dbConfig.setSortedDuplicates(true); Database db = env.openDatabase(txn, "mydatabase", dbConfig);
The main abstraction of the library: represents a configured connection to database and provides a way to execute callbacks in transactions.
Usually you'll need only single instance of this in your application, unless you need to connect several different databases or need different default settings for different use cases.
At the present moment, this file defines methods which will at some point be moved to to the external database interface. There are a bunch of the unimplemninted interface that used to be in this file. They have been moved to old_Database.java. old_Database.java is checked into the codeline but is not built, it is there for reference
A database application generally begins processing by accessing one or more critical objects and proceeding from there. These objects are root objects, because they lead to interconnected webs of other objects. The ability to name an object (using method bind) and retrieve it later by that name (using method lookup facilitates this start-up capability. A name is not explicitly defined as an attribute of an object. Naming an object also makes it persistent.
There is a single flat name scope per database; thus all names in a particular database are unique. @author David Jordan (as Java Editor of the Object Data Management Group) @version ODMG 3.0
A database is a collection of prototypes, as loaded from the internal file fuzzers.jbrofuzz residing within the JBroFuzz.jar file.
Once a database instance has been created, you can obtain any known fuzzer through the factory method {@link #createFuzzer(String,int)}.
This class involves a number of further methods for querying the number of prototypes available, their corresponding IDs, names, as well as payload values.
@author subere@uncon.org @version 1.9 @since 1.2Database is an encapsulation of the database driver functionality that is necessary to access an XML database. Each vendor must provide their own implmentation of the Database interface. The implementation is registered with the DatabaseManager to provide access to the resources of the XML database. In general usage client applications should only access Database implementations directly during initialization.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |