Abstract: A database access interceptor includes a statement pool and a table buffer. The statement pool and the table buffer are associated with physical database connections. The interceptor may include a separate instance of the statement pool for each physical database connection. Similarly the interceptor may include a separate instance of the table buffer for each physical database connection.

Abstract: In an embodiment, a database interface performs a three-step optimistic database access. The database interface initially performs an optimistic read of a database object. The database object is checked for consistency after the optimistic read. If the database object is inconsistent, a first pessimistic read is performed with an isolation level that does not guarantee consistency (e.g., with an isolation level of committed read). The database object is checked again for consistency after the first pessimistic read. If the database object is inconsistent, a second pessimistic read is performed with an isolation level that may guarantee consistency (e.g., with an isolation level of repeatable read).

Abstract: A system and method are provided for a query language mapping architecture. In an embodiment, the query language mapping architecture includes an Enterprise Java Bean (EJB) interpreting layer to receive one or more EJB persistence requests and to translate the one or more EJB persistence requests to command sequences. In an embodiment, the query language mapping architecture may also include a Structured Query Language (SQL) assembly layer to receive the command sequences from the EJB interpreting layer and to assemble one or more SQL statements based, at least in part, on the command sequences.

Abstract: A system and method are provided for interacting with a persistence layer. In an embodiment, a persistence layer may receive a representation of Enterprise Java Bean (EJB) metadata. The persistence layer may determine whether the representation of Enterprise Java Bean (EJB) metadata is compatible with a version of the EJB specification. In an embodiment, a representation of an Object-Relational (OR) mapping schema may be generated based, at least in part, on the representation of EJB metadata.

Abstract: A system and method are provided for communicating with a Structured Query Language (SQL) statement generator. In an embodiment, an SQL mapper factory receives an object-relational mapping schema to define a mapping between one or more persistence fields of one or more Enterprise Java Beans (EJBs) and one or more tables of a database. An SQL mapper implementation may be selected based, at least in part, on a value specified in a properties file. In an embodiment, the SQL mapper implementation may be generated based, at least in part, on the object-relational mapping schema.

Abstract: In an embodiment, a database interface performs a three-step optimistic database access. The database interface initially performs an optimistic read of a database object. The database object is checked for consistency after the optimistic read. If the database object is inconsistent, a first pessimistic read is performed with an isolation level that does not guarantee consistency (e.g., with an isolation level of committed read). The database object is checked again for consistency after the first pessimistic read. If the database object is inconsistent, a second pessimistic read is performed with an isolation level that may guarantee consistency (e.g., with an isolation level of repeatable read).

Abstract: A system and method are provided for interacting with a persistence layer. In an embodiment, a persistence layer may receive a representation of Enterprise Java Bean (EJB) metadata. The persistence layer may determine whether the representation of Enterprise Java Bean (EJB) metadata is compatible with a version of the EJB specification. In an embodiment, a representation of an Object-Relational (OR) mapping schema may be generated based, at least in part, on the representation of EJB metadata.

Abstract: A system and method are provided for a query language mapping architecture. In an embodiment, the query language mapping architecture includes an Enterprise Java Bean (EJB) interpreting layer to receive one or more EJB persistence requests and to translate the one or more EJB persistence requests to command sequences. In an embodiment, the query language mapping architecture may also include a Structured Query Language (SQL) assembly layer to receive the command sequences from the EJB interpreting layer and to assemble one or more SQL statements based, at least in part, on the command sequences.

Abstract: A database access interceptor includes a statement pool and a table buffer. The statement pool and the table buffer are associated with physical database connections. The interceptor may include a separate instance of the statement pool for each physical database connection. Similarly the interceptor may include a separate instance of the table buffer for each physical database connection.