# US 2026/0093677 A1 · Native object versioning

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0093677 A1
- Document ID: US20260093677A1
- Status: Published application
- Kind: A1
- Application number: 18/902,802
- Filed: 2024-09-30
- Published: 2026-04-02
- Earliest claimed: 2024-09-30
- Assignees: Teradata US, Inc.
- Applicants: Teradata US, Inc.
- Inventors: Denis Molin
- Web page: https://patentgrep.com/patent/US20260093677A1

## CPC

- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system may include a storage device and at least one processor in communication with the storage device. The at least one processor may receive a query that comprises a reference to at least one data object. The at least one processor may identify a locally-stored version of the at least one data object. The at least one processor may retrieve a current version of the at least one data object. The at least one processor may compare the locally-stored version and the current version of the at least one data object. The at least one processor may, in response to the locally-stored version being different than the current version, update the locally-stored version to the current version. The at least one processor may execute the query based on the current version of the at least one data object. A method and computer-readable medium are also disclosed.

## Claims

### Claim 1

A system comprising:
a storage device;
at least one processor in communication with the storage device, the at least one processor configured to:
receive a query that comprises a reference to at least one data object;
identify a locally-stored version of the at least one data object;
retrieve a current version of the at least one data object, wherein the current version is maintained in a remotely-stored data structure;
compare the locally-stored version and the current version of the at least one data object;
in response to the locally-stored version being different than the current version, prior to execution of the query, update the locally-stored version to the current version; and execute the query based on the current version of the at least one data object.

### Claim 2 (depends on 1)

The system of claim 1, wherein each data object has a version identifier, wherein the at least one processor is configured to:
compare the locally-stored version identifier and the current version identifier of the at least one data object; and
in response to the locally-stored version identifier being different than the current version identifier, update the locally-stored version to the current version.

### Claim 3 (depends on 2)

The system of claim 2, wherein an initial data object identifier is generated upon creation of the data object.

### Claim 4 (depends on 1)

The system of claim 1, wherein the locally-stored version of the data object is stored in local storage of the system.

### Claim 5 (depends on 1)

The system of claim 1, wherein the data object is a table or a view.

### Claim 6 (depends on 1)

The system of claim 1, wherein the at least one data object is a view, and wherein the at least one processor is further configured to;
identify ancestor levels of the view;
beginning with the next-to-lowest level of the ancestor levels, compare locally-stored versions of each data object at each ancestor level to current versions of each data object at the ancestor level;
in response to each locally-stored version of each data object being different than the current version at each ancestor level, update the locally-stored version to the current version; and
execute the query based on a current version of the view.

### Claim 7 (depends on 1)

The system of claim 1, wherein data object names and associated current version identifiers are maintained in a centralized repository.

### Claim 8

A method comprising:
receiving, with a processor, a query that comprises a reference to at least one data object; identifying, with the processor, a locally-stored version of the at least one data object;
retrieving, with the processor, a current version of the at least one data object, wherein the current version is maintained in a remotely-stored data structure;
comparing, with the processor, the locally-stored version and the current version of the at least one data object;
in response to the locally-stored version being different than the current version, updating, with the processor, the locally-stored version to the current version; and
executing, with the processor, the query based on the current version of the at least one data object.

### Claim 9 (depends on 8)

The method of claim 8, wherein each data object has a version identifier, wherein method further comprises:
comparing, with the processor, the locally-stored version identifier and the current version identifier of the at least one data object; and
in response to the locally-stored version identifier being different than the current version identifier, updating, with the processor, the locally-stored version to the current version.

### Claim 10 (depends on 9)

The method of claim 9, wherein an initial data object identifier is generated upon creation of the data object.

### Claim 11 (depends on 8)

The method of claim 8, wherein the locally-stored version of the data object comprises a data structure listing version ancestors.

### Claim 12 (depends on 8)

The method of claim 8, wherein the data object is a table or a view.

### Claim 13 (depends on 8)

The method of claim 8, wherein the at least one data object is a view, and wherein the method further comprises:
identifying, with the processor, ancestor levels of the view;
beginning with the next-to-lowest level of the ancestor levels, comparing, with the processor, locally-stored versions of each data object at each ancestor level to current versions of each data object at the ancestor level;
in response to each locally-stored version of each data object being different than the current version at each ancestor level, updating, with the processor, the locally-stored version to the current version; and
executing, with the processor, the query based on a current version of the view.

### Claim 14

A non-transitory computer-readable medium encoded with a plurality of instructions executable by a processor, the plurality of instructions comprising:
instructions to receive a query that comprises a reference to at least one data object;
instructions to identify a locally-stored version of the at least one data object;
instructions to retrieve a current version of the at least one data object, wherein the current version is maintained in a remotely-stored data structure;
instructions to compare the locally-stored version and the current version of the at least one data object;
in response to the locally-stored version being different than the current version, instructions to update the locally-stored version to the current version; and
instructions to execute the query based on the current version of the at least one data object.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein each data object has a version
identifier, and wherein the plurality of instructions further comprises:
instructions to compare the locally-stored version identifier and the current version identifier of the at least one data object; and
in response to the locally-stored version identifier being different than the current version identifier, instructions to update the locally-stored version to the current version.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein an initial data object identifier is generated upon creation of the data object.

### Claim 17 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the locally-stored version of the data object comprises a data structure listing version ancestors

### Claim 18 (depends on 14)

The non-transitory computer readable-medium of claim 14, wherein the data object is a table or a view.

### Claim 19 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the at least one data object is a view, and wherein the plurality of instructions further comprises:
identifying, with the processor, ancestor levels of the view;
beginning with the next-to-lowest level of the ancestor levels, instructions to compare locally-stored versions of each data object at each ancestor level to current versions of each data object at the ancestor level;
in response to each locally-stored version of each data object being different than the current version at each ancestor level, instructions to update the locally-stored version to the current version; and
instructions to execute the query based on a current version of the view.

### Claim 20 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein data object names and associated current version identifiers are maintained in a centralized repository.
