Re: Database vs Directory Service

[Dmitry Kovalev <mitya@seismic.geol.msu.ru>]

Arnold Shore wrote:

> I think we need to keep both, rendering unto Caesar ... .  That is, retain
> the inherent directory information/schema where it is, and also provide a
> linkage mechanism to the RDBMS data.  A GUID appears key to doing that
> effectively, extending both schema to accommodate that item.  The overall
> application would draw on both information sources for end-user interaction,
> presenting a unified appearance.

Not shure about what you meant by "GUID" - as I can understand, you are going
to combine the two sources of information in your custom application, at
end-user interface level.

This is fine if you don't plan interoperability with other standard/legacy
applications on lower level. But if you have some application talking LDAP
only, and want it to use some data you currently have in RDBMS - take a look at
OpenLDAP's back-sql - it provides a means to export RDBMS as LDAP tree, tunable
to your custom needs, and requires no programming except SQL/stored procedures.

It may also help avoid unnecessary duplication of data, or simplify some
aspects of your application (in combining the data particularly),
at a cost of setting it up and authoring some amount of SQL things.

Hope I got you right, if not - I blame my limited English ;)

WBW, Dmitry