GUS Schema >> TESS::MoietyMember

This table allows TESS.Moiety to be grouped together to form complexes. There is a whole id which should considered to be the complex, and the child moiety is the member moiety (protein). There should be one TESS.MoietyMember row for each member of the complex. A complex can be build up hierarchically or left flat. I guess this might eventually become an Imp table if we start to detail the relationship.

column nulls? type description
MOIETY_MEMBER_ID no NUMBER(12,0) Primary key. Edit
WHOLE_MOIETY_ID no TESS::Moiety (NUMBER(12,0) )Link to the parent moiety. Edit
PART_MOIETY_ID no TESS::Moiety (NUMBER(12,0) )Link to the parent moiety. Edit
EXTERNAL_DATABASE_RELEASE_ID SRes::ExternalDatabaseRelease (NUMBER(12,0) )What database release did this membership come from. Edit
SOURCE_ID STRING(32) What source id did it have in the (external) database. Edit
NAME STRING(255) A descriptive name for this instance. Edit
REVIEW_STATUS_ID SRes::ReviewStatus (NUMBER(12,0) )What is the review status of this membership. Edit
MODIFICATION_DATE no DATE Edit
USER_READ no NUMBER(1,0) Edit
USER_WRITE no NUMBER(1,0) Edit
GROUP_READ no NUMBER(1,0) Edit
GROUP_WRITE no NUMBER(1,0) Edit
OTHER_READ no NUMBER(1,0) Edit
OTHER_WRITE no NUMBER(1,0) Edit
ROW_USER_ID no NUMBER(12,0) Edit
ROW_GROUP_ID no NUMBER(4,0) Edit
ROW_PROJECT_ID no NUMBER(4,0) Edit
ROW_ALG_INVOCATION_ID no NUMBER(12,0) Edit

Child tables:

Subclasses: