Table: fertility

Select data Show structure Alter table New item

Comment: One row per uninterrupted period of observation on a female; during which no possible births would have been missed. Access to rows in FERTILITY is controlled, on a per-study basis, by the PERMISSION table. Per individual, fertility intervals may not overlap. StartDate must be on or precede StopDate. Only BIOGRAPHY rows with Sex = 'F' may have related female fertility interval rows. FERTILITY rows may be related only to those BIOGRAPHY rows which have a FALSE MomOnly value. The StartDate cannot precede the EntryDate of the related BIOGRAPHY row. The StopDate cannot follow the date from the related individual's BIOGRAPHY row given by the formula (DepartDate plus (DepartDateError number of years)). Rows with a StartDate which matches the related BIOGRAPHY row's EntryDate must have a StartType value which is that of the related BIOGRAPHY row's EntryType. This condition is checked on transaction commit. Rows with a StopDate which matches the related BIOGRAPHY row's DepartDate must have a StopType value which is that of the related BIOGRAPHY row's DepartType. This condition is checked on transaction commit. Rows with a StartType flagged as Initial on the START_EVENT table must have a StartDate equal to the related BIOGRAPHY row's EntryDate. This condition is checked on transaction commit, except in the case where START_EVENT.Initial is altered. Rows with a StopType flagged as Final on the END_EVENT table must have a StopDate equal to the related BIOGRAPHY row's DepartDate. This condition is checked on transaction commit, except in the case where END_EVENT.Final is altered. TIP: Use the FERTILITIES view to see AnimId and StudyId columns. FERTILITIES is identical to this table but for the additional columns.

ColumnTypeComment
fidinteger Auto Increment [nextval('fertility_fid_seq')]Unique row identifier, and hence the unique identifier of the female fertility interval. The value of this column is automatically assigned by the system; the normal practice, which results in a system generated id, is to omit this column when inserting new rows or to supply a NULL value. The value of this column cannot be NULL. The value of this column cannot be changed.
bidintegerUnique identifier of the individual for which the row records a fertility interval. TIP: Can be used to JOIN with BIOGRAPHY.BId.
startdatedateStartdate for fertility surveillance. Date on which surveillance of fertility began. This date must not have error associated with it. These dates are conservative: if you are sure that you know about her starting on July 15 but you MIGHT know about her starting on July 1, you must choose the more conservative date, which is July 15. This value may not be NULL.
starttypecharacter(1)Reason for the start of surveillance. The vocabulary for this column is defined by the START_EVENT table. This value may not be NULL.
stopdatedateStopdate for fertility surveillance. Date on which surveillance of fertility ended. Surveillance ends when you stop seeing the animal for a long enough period of time that births could be missed. This date must not have error associated with it. These dates are conservative: if you are sure that you know about her until July 1 but you MIGHT know about her until July 15, you must choose the more conservative date which is July 1. This value may not be NULL.
stoptypecharacter(1)Cause of the end of surveillance. The vocabulary for this column is defined by the END_EVENT table. This value may not be NULL.

Indexes

PRIMARYfid
INDEXbid
INDEXstartdate
INDEXstarttype
INDEXstopdate
INDEXstoptype

Alter indexes

Foreign keys

SourceTargetON DELETEON UPDATE
bidbiography(bid)NO ACTION NO ACTION Alter
starttypestart_event(code)NO ACTION NO ACTION Alter
stoptypeend_event(code)NO ACTION NO ACTION Alter

Add foreign key

Triggers

Add trigger

Language: