| Home >> All >> com >> lutris >> appserver >> server >> [ sql Javadoc ] |
• com.lutris.appserver.server.sql: Javadoc index of package com.lutris.appserver.server.sql.
Package Samples:
• com.lutris.appserver.server.sql.informix
• com.lutris.appserver.server.sql.msql
• com.lutris.appserver.server.sql.oracle
• com.lutris.appserver.server.sql.postgresql
• com.lutris.appserver.server.sql.standard
• com.lutris.appserver.server.sql.sybase
• com.lutris.appserver.server.sql.tests
Classes:
• StandardConnectionAllocator: Manages a pool (set) of connections to a database. The pool is named as a logical database. By naming a pool, this allows connection resource control to be on a finer grain that a database and allows for easier migration to multiple databases. One or more pools can map to the same actual database. A connection considered part of the pool, even if its allocated to a thread. These objects are all publicly accessed via the Database Manager, not directly. If an error occurs in a connection, it is dropped from the pool. The process using the connection has already received an error which aborts the ...
• StandardDatabaseManager: The standard database manager implementation. A database manager manages logical databases. It provides a single object from which database connections, object ids (OIDs), transactions and queries can be obtained. The configuration file specifies what logical database to create. The configuration data is specified as follows: DatabaseManager.Databases - A list of logical SQL database names. DatabaseManager.DefaultDatabase - The default logical database used by this application. Optional, if not specified, then the first entry in "DatabaseManager.Databases" is used. DatabaseManager.Debug - Specify ...
• DBQuery: Utility for querying object from a database. Allocates connections from the database connection pool, ensures the integrity of those connections, and manages result sets after a query is performed. Returns objects representing data in the database. Example - querying a user: import com.lutris.appserver.server.LBS; import com.lutris.appserver.server.sql.*; DBQuery dbQuery = LBS.getDatabaseManager().createQuery(DATABASE_NAME); // NOTE: class CustomerQuery implements Query { ... } CustomerQuery customerQuery = new CustomerQuery(); String [] loginIds = { "customer1", "customer2" }; try { for (int idx=0; ...
• DBRowUpdateException: DBRowUpdateException is thrown when a CoreDO update fails. Two values are used to uniquely identify a row in a table: oId and version. The executeUpdate() method creates an SQL UPDATE command to write the new values in a CoreDO object back to the correct row in the database. The row is identifed by the oId and version values specified in the WHERE-clause of the UPDATE command. So, if no row has the specified oId and version combination, the UPDATE will fail, and report that 0 rows were updated. Note: other database problems (e.g. disk full) can also cause an UPDATE to fail, but these are rare. ...
• StandardLogicalDatabase: Represents a logical database. Each logical database has a connection allocator and a object id allocator. The standard implementation of a local database is used when the database is described as of type Standard in DatabaseManager.DB. dbname .ClassType The configuration data is specified in the section: DatabaseManager.DB. dbName The following is a description of the sub fields: JdbcDriver - The JDBC driver to use to access that database. Manditory. E.g. "intersolv.jdbc.sequelink.SequeLinkDriver" Connection - This section is passed onto the connection allocator. See for details on connection ...
• DBTransaction: Used to perform database transactions. Example - adding a new user: import com.lutris.appserver.server.LBS; import com.lutris.appserver.server.sql.*; DBTransaction transaction = LBS.getDatabaseManager().createTransaction(DATABASE_NAME); // NOTE: class CustomerDO implements Transaction { ... } // NOTE: An Object ID is automatically calculated by the constructor. CustomerDO customer = new CustomerDO(); customer.setFirstName("Santa"); customer.setLastName("Claus"); // ... set all other CustomerFields ... // // Now add the new object to the database. // try { transaction.insert(customer); transaction.commit(); ...
• InformixObjectIdAllocator: Informix Object ids can only be created via this manager. Ensures that all object ids are unique across all objects in this logical database. Also ensures good performance for allocating object ids. The configuration data is specified in the section: DatabaseManager.DB. dbName .ObjectId Configuration fields are: CacheSize - The number of object id's to cache between database queries. Optional, if not specified, then it defaults to 1024. MinValue - The starting number of Object ID allocation. This will only be used if the Object ID table is empty and thus is useful in development and testing. Optional, ...
• StandardObjectIdAllocator: Object ids can only be created via this manager. Ensures that all object ids are unique across all objects in this logical database. Also ensures good performance for allocating object ids. The configuration data is specified in the section: DatabaseManager.DB. dbName .ObjectId Configuration fields are: CacheSize - The number of object id's to cache between database queries. Optional, if not specified, then it defaults to 1024. MinValue - The starting number of Object ID allocation. This will only be used if the Object ID table is empty and thus is useful in development and testing. Optional, if ...
• ObjectId: Represents an object id used by LBS data objects. The object id must be unique. The combination of database URL and object id constitutes a GUID. The maximum value of an object id is DECIMAL(19,0)
• CloneableDO: Base class from which the data objects are created. Provides functionality for cloning data objects. The cloned data object will have a unique object identifier.
• ObjectIdAllocator: Defines the object id allocator. An object id allocator is an integral part of a logical database implementation. It manages the allocation of unique object ids.
• ConnectionAllocator: Defines the connection allocator. A connection allocator is an integral part of a logical database implementation. It manages a pool of database connections.
• DatabaseManager: The database management object interface. This class implementing this interface manages the database connections for one application.
• DatabaseManagerException: Exception for database manager failures. These are errors detected directly by the database manager rather than by JDBC.
• LogicalDatabase: Interface for a logical database. Each logical database must provide services for connection and object id allocation.
• PostgreSQLConnectionAllocator: An PostgreSQL database connection allocator used by the PostgreSQL logical database.
• PostgreSQLObjectIdAllocator: An PostgreSQL database object id allocator used by the PostgreSQL logical database.
• PostgreSQLDBTransaction: An PostgreSQL database transaction object used by the PostgreSQL logical database.
• PostgreSQLDBConnection: An PostgreSQL database connection object used by the PostgreSQL logical database.
• OracleConnectionAllocator: An Oracle database connection allocator used by the Oracle logical database.
• SybaseConnectionAllocator: An Sybase database connection allocator used by the Sybase logical database.
• OracleObjectIdAllocator: An Oracle database object id allocator used by the Oracle logical database.
• PostgreSQLDBQuery: An PostgreSQL database query object used by the PostgreSQL logical database.
• SybaseObjectIdAllocator: An Sybase database object id allocator used by the Sybase logical database.
• OracleDBTransaction: An Oracle database transaction object used by the Oracle logical database.
| Home | Contact Us | Privacy Policy | Terms of Service |