directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <aok...@bellsouth.net>
Subject [rms] Using rowid in secondary databases
Date Thu, 15 Apr 2004 19:04:42 GMT
Thought I'd put this out there on the directory dev list.

> -----Original Message-----
> From: Alex Karasulu [mailto:aok123@bellsouth.net]
> Sent: Thursday, April 15, 2004 2:51 PM
> To: bdbje@sleepycat.com
> Subject: [bdbje] [rms] Using rowid in secondary databases
> 
> Hi,
> 
> I'm trying to find a way to generalize the use of integers or longs as
> the primary keys of records in a master table sort of like the way row
> ids work in an RDBMS.
> 
> I'm envisioning the use of sequences to do this in a structure like
> so:
> 

http://nagoya.apache.org/jira/secure/attachment/14385/DatabaseTable.png

> 
> Now I'm sure the folks at SleepyCat thought about this one before.
> Wondering what your findings were if the use of integers and sequences
> was thought of to tie together secondary and master databases.
> 
> The reason why this is looking attractive to me is you generalize how
> the structure is glued together rather than having the master capable
> of having any kind of key.  Plus I'd like to stick as close to using
> primitives as possible for keys.
> 
> Also on a side note I was wondering if the feature that resuscitates
> the primary database entry when a lookup occurs on a secondary can be
> turned off in any way.  Sometimes an application may just want to
> scan indices and that suffices so resuscitating the data within the
> master table is wasteful in these situations.  Is there a mechanism
> for controlling this aspect of JE?
> 
> Thanks,
> Alex



Mime
View raw message