Abstract: In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table.

Abstract: Techniques for optimizing a software application include receiving, at a local computing system, a query from an application for data stored on a database table, the query including a context defined by a name of the database table; comparing the context of the query to a context of a predefined query scenario; based on the context of the query matching the context of the predefined query scenario, retrieving data stored on a secondary database replicated from data stored on a main database; and passing the retrieved data from the secondary database to the application.

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: Techniques for optimizing a software application include receiving, at a local computing system, a query from an application for data stored on a database table, the query including a context defined by a name of the database table; comparing the context of the query to a context of a predefined query scenario; based on the context of the query matching the context of the predefined query scenario, retrieving data stored on a secondary database replicated from data stored on a main database; and passing the retrieved data from the secondary database to the application.

Abstract: In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table.

Abstract: According to some embodiments, a programming language in an application server may access different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table may be mapped to a work area such that each column in the database table is mapped to a corresponding component of the work area (having a default component type based on the column type of the associated column). It may be determined that a particular column in the database table is to store large object data content, and a new mapping to a work area may be defined such that a particular column maps to a corresponding component having a component type other than the default component type.

Abstract: According to some embodiments, a programming language in an application server may access different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table may be mapped to a work area such that each column in the database table is mapped to a corresponding component of the work area (having a default component type based on the column type of the associated column). It may be determined that a particular column in the database table is to store large object data content, and a new mapping to a work area may be defined such that a particular column maps to a corresponding component having a component type other than the default component type.

Abstract: According to some embodiments, a programming language in an application server may include access to different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table, having columns to store content, each column being associated with a column type, may be mapped to a work area such that, at a database server, each column in the database table is mapped to a corresponding component of the work area, the corresponding component having a default component type based on the column type of the associated column in the database table. It may be determined that a particular column in the database table is to store large object data content, and, in response to the determination, a new mapping to a work area may be defined such that the particular column maps to a corresponding component having a component type other than the default component type.

Abstract: According to some embodiments, a programming language in an application server may include access to different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table, having columns to store content, each column being associated with a column type, may be mapped to a work area such that, at a database server, each column in the database table is mapped to a corresponding component of the work area, the corresponding component having a default component type based on the column type of the associated column in the database table. It may be determined that a particular column in the database table is to store large object data content, and, in response to the determination, a new mapping to a work area may be defined such that the particular column maps to a corresponding component having a component type other than the default component type.

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: 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 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.