Distributed database management system
First Claim
1. A method for storing a data object with dependency information, the method comprising:
- generating a dependency attribute for a first data object, the dependency attribute comprising dependency data indicative of a second data object, wherein the first data object depends on the second data object such that a client device requires the second data object to utilize the first data object;
receiving, at the client device, the first data object;
determining, at the client device, whether the database stored on the client device contains the second data object;
in response to determining that the database contains the second data object, storing the first data object in the database;
in response to determining that the database does not contain the second data object;
storing the first data object in a holding area;
in response to determining that the first data object and the second data object are stored in the holding area, storing the first data object and the second data object in the database in a single atomic transaction.
2 Assignments
0 Petitions
Accused Products
Abstract
A distributed database management system provides a central database resident on a server that contains database objects. Objects, e.g., program guide data, to be replicated are gathered together into distribution packages called “slices,” that are transmitted to client devices. A slice is a subset of the central database which is relevant to clients within a specific domain, such as a geographic region, or under the footprint of a satellite transmitter. The viewer selects television programs and Web content from displayed sections of the program guide data which are recorded to a storage device. The program guide data are used to determine when to start and end recordings. Client devices periodically connect to the server using a phone line and upload information of interest which is combined with information uploaded from other client devices for statistical, operational, or viewing models.
-
Citations
16 Claims
-
1. A method for storing a data object with dependency information, the method comprising:
-
generating a dependency attribute for a first data object, the dependency attribute comprising dependency data indicative of a second data object, wherein the first data object depends on the second data object such that a client device requires the second data object to utilize the first data object; receiving, at the client device, the first data object; determining, at the client device, whether the database stored on the client device contains the second data object; in response to determining that the database contains the second data object, storing the first data object in the database; in response to determining that the database does not contain the second data object; storing the first data object in a holding area; in response to determining that the first data object and the second data object are stored in the holding area, storing the first data object and the second data object in the database in a single atomic transaction. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for storing a data object with dependency information, the system comprising:
a client device configured to; generate a dependency attribute for a first data obj ect, the dependency attribute comprising dependency data indicative of a second data object, wherein the first data object depends on the second data object such that the client device requires the second data object to utilize the first data object; receive the first data object; determine whether the database stored on the client device contains the second data object; in response to determining that the database contains the second data object, store the first data object in the database; in response to determining that the database does not contain the second data object; store the first data object in a holding area; in response to determining that the first data object and the second data object are stored in the holding area, store the first data object and the second data object in the database in a single atomic transaction. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
Specification