Difference between revisions of "Database Table: reluser2"

From Dreamwidth Notes
Jump to: navigation, search
m (Robot: Updating page description status.)
(Robot: Updating: Format, definition)
Line 4: Line 4:
  
 
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 [[Database Table: reluser|reluser]].
 
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 [[Database Table: reluser|reluser]].
 
 
 
= Definition =
 
= Definition =
 +
<source lang="sql">
 +
CREATE TABLE reluser2 (
 +
    userid    INT UNSIGNED NOT NULL,
 +
    type      SMALLINT UNSIGNED NOT NULL,
 +
    targetid  INT UNSIGNED NOT NULL,
  
<source lang="sql">
+
     PRIMARY KEY (userid,type,targetid),
CREATE TABLE reluser (
+
    INDEX (userid,targetid)
:userid     INT UNSIGNED NOT NULL,
+
:targetid  INT UNSIGNED NOT NULL,
+
:type      char(1) NOT NULL,
+
:PRIMARY KEY (userid,type,targetid),
+
:KEY (targetid,type)
+
 
)
 
)
 
</source>
 
</source>
 
 
{{Database Table Footer}}
 
{{Database Table Footer}}

Revision as of 07:03, 28 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 reluser2 (
    userid    INT UNSIGNED NOT NULL,
    TYPE      SMALLINT UNSIGNED NOT NULL,
    targetid  INT UNSIGNED NOT NULL,
 
    PRIMARY KEY (userid,TYPE,targetid),
    INDEX (userid,targetid)
)

Relationships

Outgoing

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