Pre-Grant Publication Number: 20070124317
Database staging area read-through or forced flush with dirty notification
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application. Peer To Patent forwards the Top 10 most relevant prior art submissions and their annotations to the USPTO.

Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Annotations(3)
#18OpenLDAP Proxy Cache Extension
Applies to Claims 1
Submitted by: Tim BolshawCreated: almost 5 years ago
2 thumbs up 4 thumbs down
Summary / Description
Summary / DescriptionCaching of queries from multiple data stores (in this case directories) that may be from similar or different types of backend databases.
 
Basic Information
Type of Prior ArtOnline Publication
 
URLhttp://www.openldap.org/lists/o...
 
Author/CreatorJonghyuk Choi <jongchoi@us.ibm.com>, Apurva Kumar of IBM India Research
 
TitleProxy Cache Contribution
 
Publication DateMarch 12, 2003
 
Publisher
 
Directions to Document Location
 
Additional Information
 
Notes / To Do
NotesPlease can others help connect this to individual claims as I am not legally trained and have limited time. I just wanted to ensure this clearly relevant information was out there. The actual code was committed to the OpenLDAP repository earlier than
 
Excerpt
Excerpt
The proxy cache provides the following features : 1. Semantic caching of positive conjunctive LDAP queries 2. Attribute level caching. 3. Consistency support 4. Support for multiple backend types 5. Support for caching multiple directories 6. Support for multiple database instances for a single cache directory tree.
 
Relevance
Claims
1
A method for managing data in an operational datastore and a staging datastore comprising: configuring the staging datastore, comprising: (a) defining a relationship between one or more fields of a first data structure in the staging datastore and one or more fields of a second data structure in the operational datastore, wherein the first data structure is a data source for the second data structure in the operational datastore; and (b) defining a first query comprising at least one field in the first data structure on which the relationship between the data structures is defined, the first query being configured to query and retrieve data from the first data structure; periodically migrating data from the first data structure to the second data structure according to the defined relationship, wherein the migrating occurs in response to a predefined condition being met; receiving a user defined query configured to query and return data from the operational datastore; in response to receiving the user defined query, executing the first query to retrieve, from the first data structure, any non-migrated data relevant to the user defined query; in the event any non-migrated data relevant to the user defined query are returned, transforming the returned non-migrated data into a format consistent with the format of the second data structure; executing the user defined query against a data set including the second data structure and the transformed data; and returning results for the executed user defined query.
Relevance
Directories, both local and remote, can be linked. Queries can be cached.
Directories, both local and remote, can be linked. Queries can be cached.
Claim Chart
Some
0 days left
Activity
Application
Discussion (24)
Prior Art (4)
Research (9)
Subscribe to this Community
Invite a Reviewer
HOW TO USE PEER TO PATENT
Peer To Patent Videos