Issue #3: Provide applicable operational attributes. - slapi-nis

slapi-nis

#3 Provide applicable operational attributes.

Closed: Fixed None Opened 15 years ago by nalin.

When constructing new entries, adding the same operational attributes which the default database plugin does (or at least the ones which are applicable) would let them be used in query filters. Mainly I'm thinking about "entrydn" and "parentid", but there might be other stuff that's interesting if not useful.

nalin commented 15 years ago

The interesting attributes defined with usage "directoryOperation" in the default schema are:
createTimestamp (GeneralTime)
modifyTimestamp (GeneralTime)
creatorsName (DN)
modifiersName (DN)
* entryDN (DN)

nalin commented 15 years ago

Fixed. Also added "numSubordinates" and "hasSubordinates" calculation. I don't think that the container entry for our top-level is something we want to mess with, though, so it's not completely seamless.

Metadata

Assignee

nalin

Tags

None

Blocking

None

Depending on

None

Milestone

Someday

rhbz

None

blockedby

None

blocking

None

slapi-nis

Source Code

Documentation

#3 Provide applicable operational attributes. Closed: Fixed None Opened 15 years ago by nalin.

Metadata

#3 Provide applicable operational attributes.

Closed: Fixed None Opened 15 years ago by nalin.