Brian, Actually we have implemented a rudimentary relational database (non-sql) inside the server specifically to optimize for LDAP, however the engine core could be reused for an RDBMS. Both and RDBMS and an LDAP server are databases really. Actually the combination of an RDBMS coupled with an LDAP server would be very powerful together. If the data dictionary of an RDBMS is stored in LDAP the schema remains consistant across RDBMS instances and can be managed centrally and replicated easily. Also works nicely for the storage of simple LUT based contraint tables. You know the ones u use for an enumeration of options to constrain a column. For example a LOAN table may have a TYPE column and there may be a LOAN_TYPES lookup table to constrain the column containing a single pk column of loan type varchars like so: Jumbo 30 Year Fixed 15 Year Fixed 5 Year ARM etc ... LDAP would be great for storing LUT's where the reads are many and the writes are few. It's not a core table for transactions like the LOAN table itself. This way several databases can leverage the same LUT data consistantly. Also you can use delegation in LDAP to let the designated authority manage the additions to the LOAN_TYPES table. Another member on the LDAPd team named Robb which is CC'ed in this email has been discussing the potential for a common database library. The library would have a storage managment layer, a index and a search engine with an optimizer for use in any database paradigm. Robb's an ex Oracle developer that helped design what is to be the system catalog for LDAPd. He's valuable to us from a db engineering standpoint. I'm sure he could play a pivitol role in working with the db folks. But please don't take him from us just yet ;-). BU, Alex > > From: Brian McCallister <[EMAIL PROTECTED]> > Date: 2003/09/11 Thu PM 12:27:01 EDT > To: [EMAIL PROTECTED] > Subject: Re: Official Apache Directory Project Proposal Submission > > Am writing up a post, but you might also want to say something about > this on [EMAIL PROTECTED] as an LDAP is sort of a db =) > > A high-profile new project could help liven up DB some ;-) > > -Brian > > On Wednesday, September 10, 2003, at 03:53 PM, <[EMAIL PROTECTED]> > wrote: > > > We're at the disposal of the Incubator and hope to find answers to > > these policy questions ourselves. In the LDAPd project for example we > > followed Apache rules for accepting committers to the best of our > > abilities. Where ever possible we try to follow the Apache way. > > Hopefully Nicola and those at the incubator can shed more light on how > > best to proceed and what policies to adopt. > > > > Sincerely, > > Alex Karasulu > > > >> > >> From: Brian McCallister <[EMAIL PROTECTED]> > >> Date: 2003/09/10 Wed PM 03:00:12 EDT > >> To: [EMAIL PROTECTED] > >> Subject: Re: Official Apache Directory Project Proposal Submission > >> > >> What are voting rules (ie, who is eligible for binding votes for > >> acceptance into the incubator, incubator committers, committers at > >> large, etc?) > >> > >> -Brian McCallister > >> > >> On Wednesday, September 10, 2003, at 02:37 PM, <[EMAIL PROTECTED]> > >> wrote: > >> > >>> On behalf of the Apache members and LDAPd members associated with > >>> this > >>> perspective Incubator podling, I officially submit the Incubator > >>> proposal for what will eventually become the Apache Directory > >>> Project. > >>> The proposal document is online here as a wiki: > >>> > >>> http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheDirectoryProject > >>> > >>> Thanks much, > >>> Alex Karasulu > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
