DATA CAVEATS FOR DATABASE TABLES

• US 20140214828A1
• Filed: 08/20/2013
• Published: 07/31/2014
• Est. Priority Date: 01/28/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Buco, Melissa J., DIAO, Yixin, LOEWENSTERN, David M., PINEL, Florian, SHWARTZ, Larisa
• Granted Patent: US 8,996,521 B2
• Time in Patent Office: Days
• US Class Current: 707/736
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/284 Relational databases

Abstract

A method for storing data caveats for databases is described. The method includes storing at least one record in at least one content table in a database. The method includes storing at least one data caveat having a relationship to the content table in at least one record in a caveat table. A data caveat has a relationship to the content table when the data caveat applies to: a record in the content table or the content table in entirety. The method also includes storing, in a memory device, an indication of the relationship. Articles of manufacture are also described.

Claims

1. A method comprising:

storing at least one record in at least one content table in a database;

storing at least one data caveat having a relationship to the content table in at least one record in a caveat table, where a data caveat has a relationship at least one of the content table or specific records in the content table; and

storing, in a memory device, an indication of the relationship.

2. The method of claim 1, where the at least one data caveat applies to the content table, and

where the indication of the relationship is embodied in a field in the caveat table.

3. The method of claim 1, where the at least one data caveat applies to the at least one content table, and

where the indication of the relationship to one or more specific record in the content table is embodied in a field in the at least one field in the content table.

4. The method of claim 3, where the field comprises at least one bit and each of the at least one bit corresponds to a record in the caveat table.

5. The method of claim 1, where storing the at least one data caveat comprises adding a record to the caveat table;

and

where storing the indication of the relationship to specific records in the content table comprises changing at least one bit in a field in the content table.

6. The method of claim 1, where each record in the caveat table comprises a field indicating content table(s) associated with the data caveat in the record, where specific records in a content table are associated with a data caveat when the data caveat has a relationship to the record in the content table indicated by values in bit in a field in the content table.

7. The method of claim 1, further comprising receiving the at least one data caveat with the at least one record in a content table.

8. The method of claim 1, further comprising:

receiving the at least one record of the content table at a first time; and

receiving the at least one data caveat at a second subsequent time.

9. The method of claim 1, further comprising:

receiving a query; and

responding to the query based at least in part on the caveat table and the content table.

10. The method of claim 9, where the query is a structured query language query.