Difference between revisions of "Database Table: reluser2"

From Dreamwidth Notes
Jump to: navigation, search
m (Robot: Converting database table to use database table header template.)
Line 1: Line 1:
{{#set:name=reluser2|table type=clustered}}
+
{{Database Table|name=reluser2|table type=clustered}}
 
[[Description::User-space (clustered) relationships table. Only used for 'hide this comm from my profile page'.]]
 
[[Description::User-space (clustered) relationships table. Only used for 'hide this comm from my profile page'.]]
 
This is in the clustered database; [[Database Table: reluser|reluser]] stores related information in the global database.
 
This is in the clustered database; [[Database Table: reluser|reluser]] stores related information in the global database.

Revision as of 11:31, 27 January 2010

"{{{repo}}}" is not in the list of possible values (dw-free, dw-nonfree) for this property. This is a clustered table. User-space (clustered) relationships table. Only used for 'hide this comm from my profile page'. This is in the clustered database; reluser stores related information in the global database.

Possible values of type are defined in get_reluser_id, in ljrelation.pl. Note that this does not take the same values as the char(1) type field in reluser.

Definition

CREATE TABLE reluser (
:userid     INT UNSIGNED NOT NULL,
:targetid   INT UNSIGNED NOT NULL,
:TYPE       CHAR(1) NOT NULL,
:PRIMARY KEY (userid,TYPE,targetid),
:KEY (targetid,TYPE)
)

Relationships

Outgoing

  • Foreign key: targetid to user.userid
  • Foreign key: userid to user.userid