| Home >> All >> org >> jdbf >> [ engine Javadoc ] |
Page 1 2
• org.jdbf.engine: Javadoc index of package org.jdbf.engine.
Package Samples:
• org.jdbf.engine.basic
• org.jdbf.engine.caching
• org.jdbf.engine.configuration
• org.jdbf.engine.criteria
• org.jdbf.engine.database
• org.jdbf.engine.keygen
• org.jdbf.engine.mapping
• org.jdbf.engine.reflection
• org.jdbf.engine.repository
• org.jdbf.engine.sql
• org.jdbf.engine.sql.connection
Classes:
• Types: Types is the class that maps the type of the property with SQLType (e.g. int with java.sql.Types.INTEGER). | type | SQL Type | |------------- |--------------------------| | int | java.sql.Type.INTEGER | | long | java.sql.Type.BIGINT | | binary | java.sql.Type.BINARY | | boolean | java.sql.Type.BIT | | date | java.sql.Type.DATE | | decimal | java.sql.Type.DECIMAL | | double | java.sql.Type.DOUBLE | | float | java.sql.Type.FLOAT | | real | java.sql.Type.REAL | | smallint | java.sql.Type.INTEGER | | time | java.sql.Type.TIME | | timestamp | java.sql.Type.TIMESTAMP | | tinyint | java.sql.Type.TINYINT ...
• XPathManager: XPathManager is the class that parses the informations on the repository and finally it creates an RepositoryView. To create a RepositoryView, XPathManager uses the XPath that specifies the path the repositoryView on the repository file. XPath is express as /repository/repositoryView/[name='repositoryName'], where repositoryName is the name of repository which needs to return the informations. These informations are: BeanDescriptor ItemDescriptor
• HighLowMap: The class provides mapping information for generation of keys using a key-values table. This is not the HighLow approach described by Scott Ambler in his paper titled Mapping Objects To Relational Databases Scott Ambler calls this the key-values approach, but others use "HighLow" to describe a modified key-values approach which does not use database access for each key.
• KeyKeeper: This class provides generated keys. The method is similar to the one called Key-Values by Scott Ambler in Mapping Objects to Relational Databases . With this method, there's a multi-row table which has three columns, one for the identifier for the table name, one for the identifier for the key table and another for the next key value for that table.
• SqlInterface: This class implements a part of RelationalDatabase It provides methods to build sql strings and statements and to convert data values into sql strings. It supports the ANSI standard SQL clauses. Subclasses will override the appropriate method to support extensions to ANSI SQL. Giovanni Martone
• HighLowKeyGenerator: This is not the HighLow approach described by Scott Ambler in Mapping Objects To Relational Databases . Scott Ambler calls this the key-values approach, but others use "HighLow" to describe a modified key-values approach which does not use database access for each key.
• MaxKeyGenerator: MaxKeyGenerator representes the key generator that creates OID Obtains a key by adding 1 to the highest key in the table. This class has been developed on Max approach described by Scott Ambler in Mapping Objects To Relational Databases .
• RepositoryView: RepositoryView is the class that represents the repositoryView specified in repository. His purpose is that to map the informations of Java object to RDBMS. In this way RepositoryView can fills and returns the Java object after the queries are executed.
• DeleteStatement: DeleteStatement is that class that represents the delete sql statement. DeleteStatement handles the creation of sql statement with the informations specified in a RepositoryView object and provides to execute the delete statement.
• InsertStatement: InsertStatement is that class that represents the insert sql statement. InsertStatement handles the creation of sql statement with the informations specified in a RepositoryView object and provides to execute the insert statement.
• SelectStatement: SelectStatement is that class that represents the select sql statement. SelectStatement handles the creation of sql statement with the informations specified in a RepositoryView object and provides to execute the select statement.
• UpdateStatement: UpdateStatement is that class that represents the update sql statement. UpdateStatement handles the creation of sql statement with the informations specified in a RepositoryView object and provides to execute the update statement.
• ConnectionSource: This class provides an object Connection.i ConnecitonSource contains the state of connection also.When a connection has is got by ConnectionManager, it is marked as in use and it is locked until releaseConnection method is invoked.
• DatabaseImpl: DatabaseImpl is the class that handles the operations against database. DatabaseImpl handles the operations on transaction. These operations are: begin close commit rollback
• SQLStatement: SQLStatement is an abstract class that represents the sql statement. SQLStatement handles the creation of sql statement with the informations specified in a RepositoryView object.
• Transaction: A transaction context is required in order to perform operations against the database. The only way to begin a new transaction is through the creation of a new transaction.
• TransactionImpl: A transaction context is required in order to perform operations against the database. The only way to begin a new transaction is through the creation of a new transaction.
• RepositoryFactory: RepositoryFactory is a factory of Repository. Collection of Repository are loaded on startup and are putted in this class so they are available.
• QueryResults: QueryResults is the class-mapped equivalent of a JDBC ResultsSet . These are the results produced by the given SelectStatement .
• SqlServerInterface: It's overrides SqlInterface's methods for constructing sql statements where MS SQL Server implementation differs from ANSI or is not specified by ANSI.
• InterbaseInterface: It's overrides SqlInterface's methods for constructing sql statements where Interbase's implementaion differs from ANSI or is not specified by ANSI.
• MySQLInterface: It's overrides SqlInterface's methods for constructing sql statements where Interbase's implementaion differs from ANSI or is not specified by ANSI.
• PostgreSQLInterface: It's overrides SqlInterface's methods for constructing sql statements where Interbase's implementaion differs from ANSI or is not specified by ANSI.
• OracleInterface: It's overrides SqlInterface's methods for constructing sql statements where Oracle's implementation differs from ANSI or is not specified by ANSI.
• SybaseInterface: It's overrides SqlInterface's methods for constructing sql statements where Sybase's implementaion differs from ANSI or is not specified by ANSI.
| Home | Contact Us | Privacy Policy | Terms of Service |