personinterest table

personinterest Table (15)

Link-table between person and interests in PersInt. Note; person.activeInterests must be kept in sync with the rows here whose interest in PersInt is not deleted, since that is what sets the interest indicator. Replication note; The combination of person_id and pinterest_idx is unique. If a duplicate is made on a replicated database, the system will replace the record in the target database with the one derived from the source database during replication. Therefore, do not assume that a record in this table will retain its ID indefinitely, even if the person keeps the interest.

Fields

Name	Description	Type	Nullable
personinterest_id	Primary key	PK	No
person_id	Owning person	FK person	No
pinterest_idx	Person interest link	FK PersInt	No
startDate	Start date for this interest - no GUI	DateTime	Yes
endDate	End date for this interest - no GUI	DateTime	Yes
flags	Spare flag field	UInt	Yes
registered	Registered when	UtcDateTime	No
registered_associate_id	Registered by whom	FK associate	No
updated	Last updated when	UtcDateTime	No
updated_associate_id	Last updated by whom	FK associate	No
updatedCount	Number of updates made to this record	UShort	No

personinterest table relationship diagram

Indexes

Fields	Types	Description
pinterest_idx	FK	Index
startDate	DateTime	Index
endDate	DateTime	Index
person_id, pinterest_idx	FK, FK	Unique
person_id	FK	Clustered

Relationships

Table	Description
associate	Employees, resources and other users - except for External persons
PersInt	PersInt list table. List of Person interests.
person	Persons

Replication Flags

Area Management controlled table. Contents replicated to satellites and traveller databases.
Replicate changes UP from satellites and travellers back to central.
Copy to satellite and travel prototypes.

Security Flags

Sentry controls access to items in this table using user’s Role and data rights matrix on the table’s parent.

Overview

Getting started