View: fertilities

Comment: One row per uninterrupted period of observation on a female; during which no possible births would have been missed. This view is identical to the FERTILITY table, but for the addition of the StudyId and AnimId columns. This view is updatable. The underlying rows may be changed by INSERT, UPDATE, or DELETE on the view. The BId value of the underlying FERTILITY row may be manipulated via FERTILITIES using either the BId column or the AnimId and StudyId column combination. On INSERT either BId or the AnimId/StudyId pair can be omitted from the list of inserted columns or the NULL value used in either Bid or the AnimId/StudyId pair. The BId of the underlying FERTILITIES row is assigned based on the supplied non-NULL value(s). On INSERT if both the BId and AnimId/StudyId pair are specified then the 2 values must refer to the same mother. On UPDATE if both the BId and the AnimId/StudyId pair change then the values must refer to the same mother; if only one of the BId or the AnimId/StudyId pair changes then the changed value(s) is(are) used. For more information see the FERTILITY table documentation.

ColumnTypeComment
fidinteger NULLUnique 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.
bidinteger NULLUnique identifier of the individual for which the row records a fertility interval. TIP: Can be used to JOIN with BIOGRAPHY.BId.
studyidcharacter varying(12) NULLIdentifier of the study for which the individual is observed. This value may not be NULL. TIP: Can be used to JOIN with STUDY.Id.
animidcharacter varying(16) NULLThe identifier used by the study to denote the individual. This value may not be NULL.
startdatedate NULLStartdate 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) NULLReason for the start of surveillance. The vocabulary for this column is defined by the START_EVENT table. This value may not be NULL.
stopdatedate NULLStopdate 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) NULLCause of the end of surveillance. The vocabulary for this column is defined by the END_EVENT table. This value may not be NULL.
Language: