StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11413499
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-07-10T12:37:45.747
FavoriteCount
0
LastActivityDate
2012-07-10T12:37:45.747
LastEditDate
LastEditorUserId
0
OwnerUserId
810802
ParentId
11411847
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<h3>The Root DSE and possible base DN of the schema</h3> <p>Assuming that the LDAP client only cares what attributes are defined in the schema (see <code>extensibleObject</code> below), to determine if an <code>attribute</code> is defined in the server schema, retrieve the schema. In many directory servers, the base DN (or base object) for the schema is defined in the attribute <code>subSchemaSubEntry</code> which might be present in the root DSE. For more information about the root DSE, see <a href="https://ff1959.wordpress.com/2011/04/11/the-root-dse-is-that-entry-with-zero-rdns-and-contains-information-about-the-directory-server/" rel="nofollow">LDAP: The Root DSE</a>. To retrieve the contents of the root DSE, transmit a search request to the server consisting of a base object of <code>''</code> and a search scope of <code>base</code>, and a requested attribute list consisting of <code>*</code> and <code>+</code>.</p> <h3>extensibleObject</h3> <p>Note that the presence of the objectClass <code>extensibleObject</code> allows LDAP clients to add any attribute name and value they require, much like a FORTRAN garbage common block, that is, attributes could be present in an entry but not defined in the schema.</p> <h3>subSchemaSubEntry not present</h3> <p>If the <code>subSchemaSubEntry</code> attribute is not present, contact the server administrators and ask for information regarding retrieving the schema and for sufficient access rights to do so.</p> <h3>subSchemaSubEntry present</h3> <p>If the <code>subSchemaSubEntry</code> attribute is present, read the schema by transmitting a search request to the server using the value of the <code>subSchemaSubEntry</code> attribute as the base object, a search scope of <code>one</code> and a requested attribute list consistent of <code>*</code> and <code>+</code>. The attribute type definitions and objectClass definitions are contained in the schema.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to retrieve all the attributes of LDAP database
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTerry Gardner
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COI'm not sure what you answered there.
  singulars
  PostPostId
  PO
  UserUserId
  USBurhan Khalid
2. COHow to access and read the attributes and object classes defined in the server schema. The question asked how to know which attributes are defined in the schema.
  singulars
  PostPostId
  PO
  UserUserId
  USTerry Gardner

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.