Database Schema

Table of Contents

15. Relationships between users

IV. Database Schema Browser

Updating cluster: 0 -

abuse_mail -

acctcode - Keeps track of valid invite codes and who has used them. To see why they were made, see table acctinvite.

acctinvite - Keeps track of generated invite codes.

acctpay - Keeps track of relationship between invite codes and payments. Some people pay to join the site before they have an account, so their invite code carries with it the knowledge that it comes with paid time.

acctpayitem -

adopt - unused. designed for the "Adopt-a-newbie" system, but never fully implemented.

adoptlast - unused. designed for the "Adopt-a-newbie" system, but never fully implemented.

authactions - When authenticating certain actions, the server generates an authaction along with some random characters (the authcode) and emails the aaid+authcode to the user to confirm they actually got it.

authnetlog -

blobcache -

bzrbalance -

bzrpayout -

bzrpot -

bzrs -

bzrvote -

bzrvoter -

captcha_session -

captchas -

ccfail -

challenges -

clients - Keeps track of clients that access the protocol. Whenever the protocol encounters a new client, a new row (and thus a new clientid) is generated.

clientusage - Keeps track of when different users use which clients, for purposes of statistics.

clustermove -

clustermove_inprogress -

clustertrack2 -

cmdbuffer - Clustered version of querybuffer. Uses specialized commands instead of general table locking

codes - Lookup table for states, countries, languages, etc...

comminterests -

community - Keeps track of properties of community accounts (which are just normal user accounts with some extra behavior)

contributed -

contributedack -

counter -

coupon -

dbinfo - For LiveJournal installations with many databases, the database connection info, roles, and weightings can be stored in the database instead of the %LJ::DBINFO hash, for easier (web-based) management.

dbweights - The dbinfo table keeps track of which databases exist. This ones keeps track of each database's roles and weights.

dirsearchres2 - Holds the results of a directory search query. userids is either "[searching]" if a query is still running, or a list of userids if it is finished.

domains - Keeps track of user-owned domain names, and which journals they map to when pointed at the LiveJournal installation's IP address.

dudata - Tracks user-based disk usage totals.

duplock - Provides a place to record that an action has been done, so it doesn't get done a second time later by a user accidentally double-clicking a single-click button in their browser. The idea is that the application should grab a write lock for both the table it's inserting into, and the duplock table. Then, check the duplock table for a duplicate. If it's already in there, unlock the tables and remember the dupid to tell the user (app should pretend it was the first time... don't show an error message!), or if it's not in there, put it in the table, and then put the resulting uniqueid from the table handler into the duplock table (as dupid). The duplock table is purged every hour or so of all locks older than an hour.

email_aliases -

events - Unused as of this writing. Part of the "subscription" system.

faq - Holds Frequently Asked Question information for the FAQ section of the support system. Alternate text can be loaded for the questions if available.

faqcat - Categories that frequently asked questions can be classified under

faquses - Tracks viewings of the individual faqs from logged-in users.

fotobilder_feedback -

friendgroup - Table describing a user's friends groups. Friends groups are used to restrict who can see an individual post, or to filter the friends view.

friendgroup2 -

friends - Table describing users someone has listed as a "friend". Also details preferences on the friend item.

includetext - Database table for storing special "include" files used in sections of the site (like the "known issues" box in support). Useful for keeping clusters of web servers in sync easier.

infohistory - A history log table for certain types of changes (like user e-mail changes). So the old values can be looked at by administrators or automatically retrieved.

interests - Table describing the different interests listed, and the number of users listing each interest.

inventory -

inviterecv -

invitesent -

keywords -

links -

log2 -

loginstall -

logprop2 -

logproplist - List of possible meta-data for journal entries.

logsec2 -

logtext2 -

meetup_ints -

meme -

memkeyword -

memkeyword2 -

memorable -

memorable2 -

ml_domains -

ml_items -

ml_langdomains -

ml_langs -

ml_latest -

ml_text -

modblob -

modlog -

moods -

moodthemedata -

moodthemes -

news_sent -

noderefs -

oldids -

openproxy -

overrides -

paidexp -

paiduser -

partialstats -

partialstatsdata -

paycredit -

payitems -

payments -

paymentsearch -

paystates -

payvars -

phonepostentry -

phonepostlogin -

phoneposttrans -

poll -

pollitem -

pollquestion -

pollresult -

pollsubmission -

portal -

priv_list - List of different admin privileges that users can have.

priv_map -

procnotify -

randomuserset -

rateabuse -

ratelist -

ratelog -

reluser -

reluser2 -

renames -

s1overrides -

s1style -

s1stylecache -

s1stylemap -

s1usercache -

s2checker -

s2compiled -

s2info -

s2layers -

s2source -

s2stylelayers -

s2styles -

schemacols -

schematables - This table is the documentation for the database tables.

secrets -

sessions -

sessions_data -

shipping -

spamreports -

stats -

statushistory -

style -

subs -

support -

supportcat - Categories for support system

supportlog -

supportnotify -

supportpoints -

supportpointsum -

supportprop -

survey_v0_8bit -

syndicated -

synitem -

sysban -

talk2 -

talkleft -

talkleft_xfp -

talkprop2 -

talkproplist - List of possible meta-data for comments.

talktext2 -

tempanonips -

themedata - Lists the system colors themes available to users.

themelist - Different color schemes. Hopefully this will die when the new style system replaces the current one.

todo -

tododep -

todokeyword -

transferinfo -

tshirtpoll -

txtmsg -

user -

userbio -

userblob -

useridmap -

userinterests -

userkeywords -

userpic -

userpic2 -

userpicblob2 -

userpicmap -

userpicmap2 -

userprop -

userpropblob -

userproplist - List of possible meta-data on users.

userproplite -

userproplite2 -

userupdate -

userusage - Keep track of when users did certain things.

weekuserusage -

zip - ZIP Code table used to validate and auto-complete data that users enter about their location. More information can be found in the redudant table zips, which was imported later.

zips - ZIP Code data for the United States that includes geographic coordinates. Only used with a ljmaint script that generates marker files for use in making xplanet maps. Most the LJ code uses the zip table instead.