A person record contains information about a person. A Midgard login account can be attached to a person record by setting the username and password fields.
Some fields in Midgard's person records are especially protected from read and write access by the backend. Be sure to read and double-check the information given in the chapters about Sitegroups and Authentication, User Management and Persons as well as with the object definition and the person functions before hunting your own fake bugs for days or reporting a bug in Midgard!
| Warning |
Be careful when you rely on the datatypes mentioned below! Some of those fields are "implicit foreign keys" that are especially critical to the integrity of your database when using replication. The Midgard functions, object methods and repligard can deal with these dependencies -- so, if you do not really know what you do, use them. |
Fields of a person record
The id of the person record.
The username of the person. If this field is empty, the person doesn't have a Midgard account. This field cannot be changed by the normal ways to update a person record, see mgd_update_password() for details.
The password of the person. It can be stored in the database either encrypted (which is the default) or in cleartext. This field cannot be changed by the normal ways to update a person record, see mgd_update_password() for details.
The first name of the person.
The last name of the person.
The date of birth of the person.
The street address of the person
The postal code (ZIP) of the person.
The city the person lives in.
The home phone number of the person.
The work phone number of the person.
The mobile phone number of the person.
The URL of the person's homepage.
The email address of the person.
A freeform information field.
A numeric field originally created to store an image id.
Bitfield of meta information about the record. Contains the bits address, phone, homepage, email and extra. These bits control which parts of the person record are public. This field cannot be changed by the normal ways to update a person record, see mgd_update_public() for details. The person objects do not offer direct (reading) access to the info field either, but encapsulate the access mask in five distinct fields of type bool.
The id of an optional topic record the person is linked to.
The id of an optional (sub) topic record the person is linked to.
The id of an optional topic describing the department the person is part of.
The id of an optional topic describing the office the person is part of.
The id of the sitegroup the person record belongs to.