This class is used for objects that contain organizational information about a user, such as the employee number, department, manager, title, office address, and so on.
Table Specific Information
All columns support server-side processing for the operators =, >= , <=, !=, LIKE, AND, and OR. Other filters are executed client side within the driver. For example, the following query is processed by LDAP:
SELECT * FROM OrganizationalPerson WHERE CN != 'NewUser' AND BaseDN = 'CN=Users,DC=MyDC' LIMIT 5You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refer to any other operators will cause an error.
To add a OrganizationalPerson, all fields can be specified except Id, DN, and BaseDN. Required fields that should be provided are RDN and ObjectClass. For example:
INSERT INTO OrganizationalPerson (RDN, ObjectClass) VALUES ('CN=NewUser', 'top;person;organizationalPerson;user;inetOrgPerson')
All columns except Id, DN, and BaseDN can be updated by providing the Id in the WHERE clause. For example:
UPDATE OrganizationalPerson SET Description = 'desc' WHERE Id = '1|CN=NewUser,CN=Users,DC=MyDC'
OrganizationalPersons can be deleted by providing the Id of the OrganizationalPerson in a DELETE statement. For example:
DELETE FROM OrganizationalPerson WHERE Id = '1|CN=NewUser,CN=Users,DC=MyDC'
Combined index and DN. Multiple indices are only possible when a column is set to SplitDataByRow.
The full distinguished name.
The relative distinguished name.
The base distinguished name.
The list of classes from which this class is derived.
This attribute contains the family or last name for a user.
The name that represents an object. Used to perform searches.
The user's password in UTF-8 format. This is a write-only attribute.
The primary telephone number.
List of distinguished names that are related to an object.
Contains the description to display for an object. This value is restricted as single-valued for backward compatibility in some cases but is allowed to be multi-valued in others. See Remarks.
Contains the user's job title. This property is commonly used to indicate the formal job title, such as Senior Programmer, rather than occupational class, such as programmer. It is not typically used for suffix titles such as Esq. or DDS.
The X.121 address for an object.
Specifies a mnemonic for an address associated with an object at a particular city location. The mnemonic is registered in the country/region in which the city is located and is used in the provision of the Public Telegram Service.
This is part of the X.500 specification and not used by NTDS.
The X.500-preferred way to deliver to addressee.
A list of alternate telex numbers.
Specifies the Teletex terminal identifier and, optionally, parameters, for a teletex terminal associated with an object.
Specifies an International ISDN Number associated with an object.
Contains telephone number of the user's business fax machine.
The street address.
The post office box number for this object.
The postal or zip code for mail delivery.
The mailing address for the object.
Contains the office location in the user's place of business.
The name of the organizational unit.
The name of a user's state or province.
Represents the name of a locality, such as a town or city.
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Defines the LDAP filter explicitly, overriding any other values set in the WHERE clause.