Patent application number | Description | Published |
20130046801 | Specifying Options in Filenames and Multiplexing the Options onto File Access Operations of a File System - Mechanisms are provided for accessing a file of a physical storage device of a data processing system via an intelligent file system associated with the physical storage device. The mechanisms receive, in the intelligent file system of the data processing system, a file access command specifying a file access operation and an extended filename. The extended filename comprises a full filename and one or more options multiplexed with the full filename. The mechanisms parse the file access command to identify the file access operation, the full filename, and the one or more options. The mechanisms then execute the file access operation on a file of the physical storage device corresponding to the full filename using the one or more options specified in the extended filename. | 02-21-2013 |
20130275476 | MANAGING RECORD LOCATION LOOKUP CACHING IN A RELATIONAL DATABASE - In managing a relational database, a relational manager sets a foreign key lookup value to an unavailable state in a source table row containing each of a foreign key value and the foreign key lookup value in a source table in a relational database, wherein the foreign key value references a primary key value in a referenced row in a separate destination table in the relational database. The relational manager, responsive to looking up, for the foreign key value, in a data structure separate from the source table, a location of the referenced row in the relational database, when the foreign key lookup value is set to the unavailable state, updating the foreign key lookup value with the location, wherein the foreign key lookup value in the source table is looked up for identifying the location of the referenced row for subsequent retrievals of the referenced row for the foreign key value. | 10-17-2013 |
20140279914 | Data Migration in a Database Management System - An approach is provided to copy records between tables in a relational database. In the approach, a Structured Query Language (SQL) table COPY statement is received with the COPY statement identifying a source table and a target table. Table column names are retrieved from a metadata that corresponds to the source table. The retrieved table column names are used to generate an SQL statement that includes an INSERT INTO clause pertaining to the target table and a SELECT clause pertaining to the source table, wherein the INSERT INTO clause includes a set of target column names and wherein the SELECT clause includes a set of corresponding source column names | 09-18-2014 |
20140280248 | ROW-BASED DATA FILTERING AT A DATABASE LEVEL - A database management system provides row based filtering of data at a database level by evaluating content of at least one record of a write data request received from an application for a particular table from among at least one table of a database, against at least one filter rule specified for the particular table. The database management system selects, for the at least one record, whether to store the at least one record of the write data request as a separate row in the particular table based on a separate action triggered for the at least one record when evaluated against the at least one filter rule specified for the particular table, each record not selected for storage being silently discarded. | 09-18-2014 |
20140280308 | Flexible Column Selection in Relational Databases - An approach is provided to expand attributes included in an SQL expansion clause into a number of selection statements. In the approach, an expansion clause is identified in within a Structured Query Language (SQL) statement with the SQL statement identifying a relational database table. Column attributes associated with the identified relational database table are compared to attributes included in the identified expansion clause. Columns included in the relational database table are then selected based on the comparison. SQL column selection statements are then generated with each of the generated SQL column selection statements corresponding to one of the selected columns. The generated SQL column selection statements are then included in the SQL statement. | 09-18-2014 |
20150339329 | ROW-BASED DATA FILTERING AT A DATABASE LEVEL - A database management system provides row based filtering of data at a database level by evaluating content of at least one record of a write data request received from an application for a particular table from among at least one table of a database, against at least one filter rule specified for the particular table. The database management system selects, for the at least one record, whether to store the at least one record of the write data request as a separate row in the particular table based on a separate action triggered for the at least one record when evaluated against the at least one filter rule specified for the particular table, each record not selected for storage being silently discarded. | 11-26-2015 |
20150347468 | GROUPING DATA IN A DATABASE - According to embodiments of the present invention, two or more attributes that are included in a plurality of attributes are aggregated into a group defined by a first data definition language syntax. The first data definition language syntax defines the group as having a groupID and one or more of an attribute definition defined in a comma-separated list and a group definition. The attribute definition is defined by a second data definition syntax. The first data definition language syntax includes the second data definition language syntax. The first data definition language syntax is structured in a manner to allow a database operation associated with the group to be applied to all attributes and/or groups included therein. | 12-03-2015 |
20160085775 | MANAGING RECORD LOCATION LOOKUP CACHING IN A RELATIONAL DATABASE - In managing a relational database, a relational manager sets a foreign key lookup value to an unavailable state in a source table row containing each of a foreign key value and the foreign key lookup value in a source table in a relational database, wherein the foreign key value references a primary key value in a referenced row in a separate destination table in the relational database. The relational manager, responsive to looking up, for the foreign key value, in a data structure separate from the source table, a location of the referenced row in the relational database, when the foreign key lookup value is set to the unavailable state, updating the foreign key lookup value with the location, wherein the foreign key lookup value in the source table is looked up for identifying the location of the referenced row for subsequent retrievals of the referenced row for the foreign key value. | 03-24-2016 |