public marks

PUBLIC MARKS from ogrisel with tag tree

October 2007

LDAP Schema Design

It is possible to make one LDAP directory serve many applications in an organisation. This has the advantage of reducing the effort required to maintain the data, but it does mean that the design must be thought out very carefully before implementation starts. LDAP directories are structured as a tree of entries, where each entry consists of a set of attribute-value pairs describing one object. The objects are often people, organisations, and departments, but can be anything at all. Schema is the term used to describe the shape of the directory and the rules that govern its content. A hypothetical organisation is described, with requirements for “white pages” directory service as well as a wide range of authentication, authorisation, and application-specific directory needs. The issues arising from the LDAP standards are discussed, along with the problems of maintaining compatibility with a range of existing LDAP clients. A plan is proposed for the layout of the directory tree, with particular emphasis on avoiding the need to re-organise it later. This involves careful separation of the data describing people, departments, groups, and application-specific objects. A simple approach to entry design is shown, based on the use of locally-defined auxiliary object classes. The effects of schema design on lookup performance are discussed. Some design tricks and pitfalls are presented, based on recent consulting experience.

February 2007

DBAzine.com: Trees in SQL: Nested Sets and Materialized Path

by 1 other (via)
Relational databases are universally conceived of as an advance over their predecessors network and hierarchical models. Superior in every querying respect, they turned out to be surprisingly incomplete when modeling transitive dependencies. Almost every couple of months a question about how to model a tree in the database pops up at the comp.database.theory newsgroup. In this article I'll investigate two out of four well known approaches to accomplishing this and show a connection between them. We'll discover a new method that could be considered as a "mix-in" between materialized path and nested sets.

Making a tree with "millions and millions" of dynamic nodes

First mail of a thread on the postgresql mailing list dealing of various ways to implement a tree structure with PostgreSQL.

Representing Trees in a relational DB

(via)
This document describes an approach for handling hierarchical data in a relational database.

ogrisel's TAGS related to tag tree

attributeType +   custom schema +   database +   hierarchical +   iana +   ldap +   modeling +   objectClass +   performance +   postgresql +   sql +