Patent US5787431A successfully refreshed from Google Patents.
US5787431A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Database development system with methods for java-string reference lookups of column names
Assignee: CODEGEAR LLC
•
Filing: 1996-12-16
•
Granted: 1998-07-28
•
Expires: 2016-12-16
Abstract
Abstract A Java-based rapid application development (RAD) environment for creating applications providing named-based programmatic access to information from columns in databases is described. For increasing the efficiency by which named-based references to database columns are processed by application programs, the system provides methodology for rapid lookups of column names, using a reference cache storing 32-bit references to immutable strings (e.g., Java strings). The reference cache is preferably constructed as a least-recently allocated cache, thereby allowing allocation to occur in a round-robin fashion, with the oldest item allocated being the first item bumped from cache when the cache overflows. Each cache entry stores a reference (e.g., four-byte pointer or handle to a string) and an ordinal entry (i.e. the corresponding database ordinal). As a reference to a particular database column occurs during execution of a program, the reference cache fills with a reference to that column name as well as the corresponding column ordinal. Accordingly, program execution proceeds with comparison of existing items in the cache, using a sequence of rapid, in-line comparisons involving simple data types (e.g., 32-bit references for the column name string). This approach minimizes the need to perform hash lookups or string comparison operations.
Inventors
- 👤 Steven T. Shaughnessy
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 07:14
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/20
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
240 words
In a development system for creating a program which includes programmatic access to columns of database tables, an improved method for determining an ordinal representing an offset within a database table of a column which has been referenced within a program by name, the method comprising: allocating memory for storing a plurality of reference cache entries, each cache entry storing a reference to a text string representing a name for a given column and further storing an ordinal for the given column; upon a request for an ordinal of a particular column, said request including the text string which represents the name for the particular column, (i) attempting to determine the ordinal by examining the reference cache for an entry storing a reference which matches a corresponding reference to a text string representing the name for the particular column; (ii) if the reference cache has no such entry, (1) determining the ordinal based, at least in part, on comparison of the text string representing the name for the particular column, and (2) updating the reference cache by storing a cache entry having a reference to the text string and the ordinal for the particular column, so that subsequent requests for the ordinal of the particular column can be satisfied based on examination of the reference cache; and (iii) providing the determined ordinal for the particular column, so that the program has programmatic access to information stored at the particular column.
Claim 2
Dependent Claim
240 words
In a development system for creating a program which includes programmatic access to columns of database tables, an improved method for determining an ordinal representing an offset within a database table of a column which has been referenced within a program by name, the method comprising: allocating memory for storing a plurality of reference cache entries, each cache entry storing a reference to a text string representing a name for a given column and further storing an ordinal for the given column; upon a request for an ordinal of a particular column, said request including the text string which represents the name for the particular column, (i) attempting to determine the ordinal by examining the reference cache for an entry storing a reference which matches a corresponding reference to a text string representing the name for the particular column; (ii) if the reference cache has no such entry, (1) determining the ordinal based, at least in part, on comparison of the text string representing the name for the particular column, and (2) updating the reference cache by storing a cache entry having a reference to the text string and the ordinal for the particular column, so that subsequent requests for the ordinal of the particular column can be satisfied based on examination of the reference cache; and (iii) providing the determined ordinal for the particular column, so that the program has programmatic access to information stored at the particular column.
Claim 3
Dependent Claim
24 words
The method of claim 1, wherein said programmatic access includes an expression in the program which references a column by a corresponding column name.
Claim 4
Dependent Claim
20 words
The method of claim 2, wherein the column name comprises a text string describing information stored by the corresponding column.
Claim 5
Dependent Claim
37 words
The method of claim 2, wherein said expression in the program which references a column by a corresponding column name includes a reference to a column data value in a form of: <database table name>. <column name>.
Claim 6
Dependent Claim
28 words
The method of claim 1, wherein each ordinal comprises an integer data value identifying a column as being located at a particular ordinal offset within a database table.
Claim 7
Dependent Claim
21 words
The method of claim 1, wherein said allocating memory step comprises: allocating memory for storing at least twenty reference cache entries.
Claim 8
Dependent Claim
27 words
The method of claim 1, wherein each reference to a particular text string comprises a fixed-length data value serving as a handle to the particular text string.
Claim 9
Dependent Claim
50 words
The method of claim 1, wherein each reference to a particular text string comprises a 32-bit data value serving as a handle to the particular text string, the particular text string itself remaining allocated by the system so long as the particular text string is being referenced within the system.
Claim 10
Dependent Claim
32 words
The method of claim 8, wherein the particular text string is deallocated by a garbage collection memory management subsystem, when the particular text string is no long being referenced within the system.
Claim 11
Dependent Claim
28 words
The method of claim 8, wherein the particular text string comprises an immutable text string whose contents cannot change while the particular text string exists within the system.
Claim 12
Dependent Claim
34 words
The method of claim 1, wherein text strings stored within the system comprise Java-compatible text strings and wherein each reference to a particular text string comprises a 32-bit quantity referencing a Java-compatible text string.
Claim 13
Dependent Claim
27 words
The method of claim 1, wherein before said updating step further includes: if the reference cache is already filled, discarding from cache the least-recently allocated cache entry.
Claim 14
Dependent Claim
36 words
The method of claim 1, wherein said comparison of the text string at step (ii)(1) includes performing a hash lookup of the text string against text strings for names of other columns of the database table.
Claim 15
Dependent Claim
36 words
The method of claim 1, wherein said comparison of the text string at step (ii)(1) includes performing a sequential lookup of the text string against text strings for names of other columns of the database table.
Claim 16
Dependent Claim
27 words
The method of claim 1, wherein subsequent requests for the ordinal of the particular column are satisfied by reading the stored ordinal directly from the reference cache.
Claim 17
Dependent Claim
28 words
The method of claim 1, wherein said subsequent requests for the ordinal occur as a result of repeated requests for the particular column within a database scan loop.
Claim 18
Dependent Claim
23 words
The method of claim 1, further comprising: employing the determined ordinal to retrieve a data value for the column from the database table.
Claim 19
Dependent Claim
27 words
The method of claim 1, wherein step (i) includes: using a sequence of rapid, in-line comparisons involving a simple data type for attempting to determine the ordinal.
Claim 20
Dependent Claim
19 words
The method of claim 18, wherein said simple data type comprises a 32-bit reference for a column name string.
Claim 21
Dependent Claim
16 words
The method of claim 18, wherein said sequence of rapid, in-line comparisons comprises integer comparison operations.
References Cited (Backward Citations)
US4961139A
Cited
US5657480A
Cited
US5465352A
Cited
US5477537A
Cited
US5724538A
Cited
US5615362A
Cited
US5526363A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-07-27 | 2002-01-26 | 2002-07-28 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-07-27 | 2006-01-26 | 2006-07-28 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-07-27 | 2010-01-26 | 2010-07-28 | $7700.00 | Window Closed / Lapsed |