Abstract: A system, medium, and method to define a database table and view based on a database model using a database language statement, the database language statement including a statement to create the table and a forward-declared JOIN statement that names the table and view, respectively and includes information regarding a relationship between at least two entities of the database.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for processing deferred clauses used in conjunction with data definition statements. The method may include receiving a data definition statement signaling creation of a database object. The received data definition statement specifies a dependency of the database object on a non-existing database object. The method may further include determining whether a deferred clause is included in the data definition statement; and based on determining that the deferred clause is included in the data definition statement, creating the database object with the dependency on the non-existing database object.

Abstract: A computer-implemented method for managing the differences in the schema of data stored in a database and the schema of data as consumed by a client application. The method involves creating additional metadata related to a property, attribute, or characteristic of a database object stored in the database, storing this additional metadata in a database catalog, and making the additional metadata available for access or retrieval by a query received from the client application for the database object stored in the database.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for modifying a database object with one or more dependent database objects. The method may include receiving a data definition statement involving a modification to a database object. The received data definition statement includes a clause imposing a restriction on the modification to the database object. The method further includes determining whether the modification results in invalidation of at least one dependent database object in response to the clause being included in the received data definition statement. Based on determining that the modification results in the invalidation of at least one dependent database object, the modification to the database object is prevented.

Abstract: Various embodiments of systems and methods for retrieving data from database are described herein. A query is received at a user application connected with a database system. The received query may be referred as a user request to retrieve data from database tables stored in the database. The query is processed and analyzed to interpret the user request for retrieving the requisite data. A return set is retrieved from the database based on the received query. Once, the required data is fetched from the database, the return set having the requisite data may be free from duplicate columns that is sent to the user application.

Abstract: In some example embodiments, a first alias creation statement is received. The first alias creation statement comprises a first table identifier of a first table, a second table identifier of a second table, a first alias identifier, and a first common table expression, and the first common table expression comprises the first table identifier. A first alias for the second table is generated based on the first alias creation statement, with the first alias comprising the first alias identifier and the first common table expression. The first alias is stored as metadata of the second table. A first query statement is received, with the first query statement comprising the second table identifier and the first alias identifier, and the first query statement is rewritten using the first common table expression based on the first alias identifier to generate a first rewritten query statement.

Abstract: Embodiments include a metadata application programming interface (API) for processing ad hoc database queries. Embodiments can be configured to process ad hoc database queries to determine the structure of the resulting data set and to provide metadata in the form of a result table, for example, in response to the queries that describes the structure of the data to be accessed by the queries. In one embodiment, this may be performed without accessing the data that would be retrieved upon executing the query. Certain embodiments may be adapted to prevent execution of the query and to return the metadata describing the structure of the data structure(s) in the resulting data set. A new “describe” statement can be incorporated into a query language expression and configured to work in a functionally coordinated manner with the API to implement a “describe” function in accordance with the techniques described in this disclosure.

Abstract: A system, medium, and method to define a database table and view based on a database model using a database language statement, the database language statement including a statement to create the table and a forward-declared JOIN statement that names the table and view, respectively and includes information regarding a relationship between at least two entities of the database.

Abstract: A computer-implemented method for managing the differences in the schema of data stored in a database and the schema of data as consumed by a client application. The method involves creating additional metadata related to a property, attribute, or characteristic of a database object stored in the database, storing this additional metadata in a database catalog, and making the additional metadata available for access or retrieval by a query received from the client application for the database object stored in the database.

Abstract: Various embodiments of systems and methods for retrieving data from database are described herein. A query is received at a user application connected with a database system. The received query may be referred as a user request to retrieve data from database tables stored in the database. The query is processed and analyzed to interpret the user request for retrieving the requisite data. A return set is retrieved from the database based on the received query. Once, the required data is fetched from the database, the return set having the requisite data may be free from duplicate columns that is sent to the user application.

Abstract: In some example embodiments, a first alias creation statement is received. The first alias creation statement comprises a first table identifier of a first table, a second table identifier of a second table, a first alias identifier, and a first common table expression, and the first common table expression comprises the first table identifier. A first alias for the second table is generated based on the first alias creation statement, with the first alias comprising the first alias identifier and the first common table expression. The first alias is stored as metadata of the second table. A first query statement is received, with the first query statement comprising the second table identifier and the first alias identifier, and the first query statement is rewritten using the first common table expression based on the first alias identifier to generate a first rewritten query statement.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for modifying a database object with one or more dependent database objects. The method may include receiving a data definition statement involving a modification to a database object. The received data definition statement includes a clause imposing a restriction on the modification to the database object. The method further includes determining whether the modification results in invalidation of at least one dependent database object in response to the clause being included in the received data definition statement. Based on determining that the modification results in the invalidation of at least one dependent database object, the modification to the database object is prevented.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for processing deferred clauses used in conjunction with data definition statements. The method may include receiving a data definition statement signaling creation of a database object. The received data definition statement specifies a dependency of the database object on a non-existing database object. The method may further include determining whether a deferred clause is included in the data definition statement; and based on determining that the deferred clause is included in the data definition statement, creating the database object with the dependency on the non-existing database object.

Abstract: Disclosed herein are system, method, and computer program product embodiments for transforming data from a first version, for example an initial version of a database, to a second version, for example a subsequent version of a database. An embodiment operates by modifying the metadata of the data to include transformational clauses, each of which describes how a portion of the data in the first version is transformed to data required by the second version.

Abstract: System, method, and computer program product embodiments transform data from a first version, for example an initial version of a database, to a second version, for example a subsequent version of a database. An embodiment includes modifying the metadata of the data to include transformational clauses, each of which describes how a portion of the data in the first version is transformed to data in the second version. Another exemplary embodiment includes differentiating between rename and add/delete operations to reduce the amount of transformational clauses included in the metadata. For example, rename operations can be identified by ignoring commonly-named columns between two versions, and identifying columns where the name has changed between the two versions while the data type has not changed.

Abstract: A method for automating evaluation of grammars associated with one or more programming languages is disclosed. The computer system accesses first grammar data associated with a first grammar and second grammar data associated with a second grammar, wherein a grammar comprises one or more rules that define a programming language. The computer system determines from the first grammar data and the second grammar data whether the first grammar and the second grammar correspond to the same programming language. Determining further includes applying one or more transformational steps to both the first grammar data and the second grammar data. After each transformational step, the computer system determines whether the first and second grammar data correspond. In accordance with a determination that the first grammar data and the second grammar data correspond, the computer system determines that the first and second grammar both correspond to the same programming language.

Abstract: Techniques for replicating data to a database include determining a change to at least one database value in a database table on a source repository; updating, based on the change to the at least one database value, a snapshot value associated with the change to the at least one database value stored in a log table; incrementing a commit value associated with the snapshot value stored in a commit table, the commit table comprising a plurality of commit values associated with a plurality of corresponding snapshot values; initiating replication of the database from the source repository to a target repository; determining a maximum commit value of the plurality of commit values; and replicating the database value in the database table from the source repository to the target repository based on the commit value associated with the snapshot value being less than or equal to the maximum commit value.

Abstract: Disclosed herein are system, method, and computer program product embodiments for transforming data from a first version, for example an initial version of a database, to a second version, for example a subsequent version of a database. An embodiment operates by modifying the metadata of the data to include transformational clauses, each of which describes how a portion of the data in the first version is transformed to data required by the second version.

Abstract: Disclosed herein are system, method, and computer program product embodiments for transforming data from a first version, for example an initial version of a database, to a second version, for example a subsequent version of a database. An embodiment includes modifying the metadata of the data to include transformational clauses, each of which describes how a portion of the data in the first version is transformed to data in the second version. Another exemplary embodiment includes differentiating between rename and add/delete operations to reduce the amount of transformational clauses included in the metadata. For example, rename operations can be identified by ignoring commonly-named columns between two versions, and identifying columns where the name has changed between the two versions while the data type has not changed.

Abstract: Techniques for replicating data to a database include determining a change to at least one database value in a database table on a source repository; updating, based on the change to the at least one database value, a snapshot value associated with the change to the at least one database value stored in a log table; incrementing a commit value associated with the snapshot value stored in a commit table, the commit table comprising a plurality of commit values associated with a plurality of corresponding snapshot values; initiating replication of the database from the source repository to a target repository; determining a maximum commit value of the plurality of commit values; and replicating the database value in the database table from the source repository to the target repository based on the commit value associated with the snapshot value being less than or equal to the maximum commit value.