Database Schema Browser


Table of Contents

abuse_mail
acctcode — Stores data on valid invite codes and who has used them. The acctinvite table stores the data on why they were made.
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
actionhistory — Global. Stores a count of generic actions. A nightly maintenance task (clean_caches) summarizes the clustered recentactions tables data here.
active_user — Clustered. Stores user activity data, such as tracking types of user activity on a per-hour basis (example: $u had login activity during this hour). An "active user" is a user who has hit a LiveJournal page while logged-in, within the specified time period. Only used if memcached servers are available, and the site administrator has not disabled active user tracking. Clustered activity data from the current or previous hour is not harvested, to avoid counting duplicates. The year, month, day, hour, and userid columns make up the primary key, for duplicate checking. Please see also active_user_summary and clustertrack2.
active_user_summary — Global. Stores user activity data. A maintenance task (clean_caches) summarizes the clustered active_user tables data here. It is indexed by year, month, day, hour, to allow multiple rows per clusterid, per hour. Only used if memcached servers are available.
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.
adsense_stat
amort_current
amort_summary
authactions — Global. Stores shared secret (authaction ID + authcode pair) data. When authenticating certain actions, the server generates an authaction along with some random characters (the authcode) and e-mails the aaid+authcode to the user to confirm they actually got it.
backupdirty — Global. Stores per-user backup status.
birthdays — Clustered. Stores unixtime of the user's next birthday. Used for sending out birthday notifications.
blobcache — Global. Generic place for code to cache blobs.
blockedcontent
blockwatch_events
botreports
botwhitelist
bzrbalance
bzrs
bzrvote
bzrvoter
captcha_session — Clustered.
captchas — Global. Stores CAPTCHAs metadata.
category
category_recent_posts
categoryjournals
categoryjournals_pending
categoryprop
categoryproplist
cc_lock
cc_usage
ccfail
cdn_map
challenges — Global. Stores data for RFC 2617 challenge-response digest authentication support - used on-site for logins, commenting, etc. Please see also secrets.
changed_profiles_list
clients — Global. Stores a record of clients that access the protocol. Whenever the protocol encounters a new client, a new row (and thus a new clientid) is generated.
clientusage — Global. Stores data of when different users use which clients, for purposes of statistics.
clustermove — Global. Stores start/completion of a user move, by moveucluster script, between database clusters. Future mass cleanings can be made during scheduled downtime using this log of where undeleted data is. It is also noted in this table if the user is to be expunged ('purged'); a note is made in the expunged_users table when the user and its data has been expunged.
clustermove_inprogress — Global. Required for user-mover script (ljumover). The script performs mass user-move operations between various clusters.
clustertrack2 — Clustered. Stores data on where users are active, for per-activity user cluster statistics. The LJ::make_user_active function updates into this table, so long as it has not already been updated for the same user within the last hour. For sites not using memcached, the table is always updated. Please see also active_user.
cmdbuffer — Clustered. This replaced the global querybuffer table. That table was used to hold queries to do later, in an efficient batch under an explicit table lock. By contrast, this table is used with specialized commands rather than general table locking.
codes — Lookup table for states, countries, languages, etc...
comet_history
comm_reader_users
commenturlsext
commercialpromo
comminterests — Global. Stores community interests. Please see also interests, which stores interest data for normal user accounts.
community — Global. Stores community accounts (which are just normal user accounts with some extra behavior) properties used.
content_flag — Global. Stores flagged content metadata. Content can be flagged as adult content, etc.
contributed
contributedack
counter — Global. Stores counter information allocated by the LJ::alloc_global_counter function. Please see also usercounter.
coupon
cprod — Clustered. Stores contextual product prodding history. This makes sure people are not pestered by specific prodding when they do not want it anymore.
cprodlist — Global. Stores contextual product prodding items. ("Hey, you've never used polls, wanna learn how?")
dbinfo — Global. Stores database connection and replication info, instead of in the %LJ::DBINFO hash, for easier (web-based) management of LiveJournal installations with many databases.
dbweights — Global. Stores each database's roles and weights. The dbinfo table keeps track of which databases exist.
delayedblob2
delayedlog2
deletion_feedback
deletion_tasks
dirmogsethandles — Global. Stores MogileFS sethandles for the Directory Search.
dirsearchres2 — Global. Stores the results of a Directory Search query.
discovery_announce_history
discovery_categories
discovery_categories_history
domains — Global. Stores user-owned domain names, and which journals they map to when pointed at the LiveJournal installation's IP address.
dudata — Clustered. Stores user-based disk usage totals.
duplock — Global. Stores a 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). This table is purged every hour or so of all locks older than an hour.
email — Global. Stores user e-mail addresses, which were historically stored in the user table.
email_aliases
email_status
emailstocks
embed_whitelist
embedcontent — Clustered.
embedcontent_preview — Clustered.
entryurlsext
eventrates
eventratescounters
eventtypelist — Global.
expunged_users — Global. Stores a log of when a user is expunged ('purged'), by the moveucluster script, so they can be queried later by time or username.
external_sites_articles_map
extuser — Global. Stores external user mappings. Note: extuser/extuserid are expected to sometimes be NULL, even though they are keyed. (Null values are not taken into account when using indexes).
faq — Global. Stores Frequently Asked Question information and their optional summaries for the FAQ section of the Support system. Alternate text can be loaded for the questions if available.
faqcat — Global. Stores categories under which Frequently Asked Questions can be classified.
faquses — Global. Stores log of viewings of individual faqs by logged-in users.
featured_photos
files
fotki_album_backup
fotki_album_prop
fotki_albums
fotki_migration_log
fotki_photo_backup
fotki_photo_prop
fotki_photos
fotki_photos_data
fotki_tag_prop
fotki_tags
fotki_tags_map
frank_text
fraudsuspects
free2pay_trx
friendgroup — Global. Stores data on a user's custom friends groups. Friends groups are used to restrict who can see an individual entry, or to filter the friends view. Please see also friendgroup2.
friendgroup2 — Clustered. Stores data on user custom friends groups.
friending_actions_q
friends — Global. Stores data of which users someone has listed as a "friend". Also stores the preferences on the friend item.
friendsfeed_ads
friendsfeed_ads_changelog
friendstimes
friendstimes2_unwatched
has_subs — Clustered. Stores ESN journal subscriptions data. A flag on event target (a journal) is written here saying whether there are known listeners out there.
homepage_cat_posts
homepage_category
homepage_items
homepage_logs
homepage_posts
identitymap — Global. Stores data for mapping a userid to an external identity and its type. This focuses on OpenID consumer support, and was introduced so infrastructure was in place to make it completely identity-system neutral rather than OpenID-specific. In theory, eventually, this will allow people to log in with TypeKey, LID, etc.
inactive_user
includetext — Global. Stores special "include" file contents used in sections of the site (like the "known issues" box in Support). Useful for keeping clusters of web servers in sync easier.
incoming_email_handle
independent_mapping
infohistory — Global. Stores a history log of certain types of changes (like user e-mail changes), so the old values can be looked at by administrators or automatically retrieved. Please see also statushistory.
interests — Global. Stores the different interests listed, and the number of users listing each interest. Please see also comminterests.
inventory
inviterecv — Clustered. Stores community invitations received.
invitesent — Clustered. Stores community invitations sent.
jabcluster — Global. Stores Jabber cluster tracking data.
jablastseen — Clustered.
jabpresence — Global. Stores Jabber presence data.
jabroster — Clustered. Stores Jabber roster data.
jabroster2
jabrostergroups2
jamrewards
jobstatus — Global. Stores worker(s) result storage status.
journal_spotlight
journalpromo
journalpromo_slot
keywords — Global. Stores userpic keywords. Please see also the clustered userkeywords table, used from data version 7.
knob — Global. Stores data for LJ::Knob, a class to efficiently support web/config-based tunables.
known_isp2
last_promotion
links — Clustered. Stores data for links users place in their Links List (“blogroll”), used in S2 styles.
ljart_artist
log2 — Clustered. Stores metadata about all journal entries. The actual content is stored in logtext2.
logbackup
loginlog — Clustered. Stores data to give users access to view their logins in the past 30 days, if they're at all afraid that their account has been compromised.
loginstall — Clustered. Stores data of failed logins, for use with the rate-limiting system.
logkwsum — Clustered. Stores the summary counts for security on entry keywords (tags).
logleft
logprop2 — Clustered. Stores metadata of entries, from possibilities stored in logproplist.
logprop_history
logproplist — Global. Stores list of possible metadata for journal entries.
logsec2 — Clustered. Stores data for mapping an entry to its security filtering. A row is added here whenever an entry with security of "usemask" (which is Friends-only and Custom) is posted. Used for speedier deleting of a friend group, which was slow since old entries needed the bit turned off in allowmask.
logtags — Clustered. Stores data for mapping of tags applied to an entry.
logtagsbackup
logtagsrecent — Clustered. Stores data for mapping tags; like logtags, but only for the most recent 100 tags-to-entry.
logtext2 — Clustered. Stores the actual text of journal entries. Data is compressed if $LJ::COMPRESS_TEXT site variable is on.
logtextbackup
loyalty_userpic_history
mailout_log
mailout_unsubscribed
manage_ratings_log
massmail_history
meetup_ints
meme
memkeyword — Global. Stores data for mapping memories to keywords. Please see also memkeyword2.
memkeyword2 — Clustered. Stores data for mapping memories to keywords.
memorable — Stores metadata for entries users mark as "Memories". Please see also the clustered memorable2 table.
memorable2 — Clustered. Stores metadata for entries users mark as "Memories".
ml_domains — Global. Stores domains of translation system
ml_items
ml_langdomains
ml_langs
ml_latest
ml_text
modblob — Clustered. Stores moderated community entry Storable objects (all props/options).
modlog — Clustered. Stores moderated community entry summary information.
moods
moodthemedata
moodthemes
mustread_block
navtag — Global. Stores data for site pages tagged using the htdocs/admin/navtag.bml tool. Site administrators can tag any URL. The tag itself is lowercase UTF-8. Some are recognized as special (FAQs, user profile pages, etc.), and users can then search by tag.
needed_backups
news_sent — Obsolete. Historic. Was used by mailusers script for sending out LiveJournal.com newsletters by e-mail.
noderefs
notificationpromo
notifyarchive — Clustered.
notifybookmarks — Clustered.
notifyqueue — Clustered. ESN event queue notification method.
notifytypelist — Global. Stores list of ESN notification class types.
offerpal
offerpal_failures
oldids — Stores globally-unique itemid and talkid ID (entries and comments), for URL compatibility. These were used pre-clustering. The LJ::get_newids function uses this table to find out what journal an old global ID belongs to and maps it to its new ID.
openid_endpoint
openid_trust
openproxy — Global. Stores open HTTP proxies data. Site administrators can set open proxy lookup sources using the @LJ::RBL_LIST site variable.
overrides — Global. Stores user S1 style system override customizations. Please see also the clustered s1overrides table.
paid_invites
paidexp
paidrepost_audience
paidrepost_settings_history
paiduser
partialstats — Global. Stores partialstats calculation times.
partialstatsdata — Global. Stores per-cluster partialstats data.
partner_registration_users
partner_registration_visits
password — Global. Stores user login passwords, which were historically stored in the user table.
payitemprop
payitems
payments
paymentsearch
paystates
paytrans
payvars
pendcomments — Clustered. Stores comments, such as OpenID comments, awaiting user approval.
perm_sale
perm_sale_200706
persistent_queue — Global table for persistent queues.
personifi_ads_cat
personifi_categories
phonepostdests
phonepostentry
phonepostlogin
phoneposttrans
pics_fotki_migrated
pics_fotobilder_migrated
pics_fotobilder_migrated_gals
pingback_history
pingrel
poll
poll2 — Clustered.
pollitem
pollitem2 — Clustered.
pollowner — Global. Stores data for mapping pollid <=> journalid.
pollprop2 — Clustered. Stores metadata of poll props used, from possibilities stored in pollproplist2.
pollproplist2 — Global. Stores list of possible metadata for polls.
pollquestion
pollquestion2 — Clustered.
pollresult
pollresult2 — Clustered.
pollresultaggregated2
pollsubmission
pollsubmission2 — Clustered.
pollsubmissionprop2
pollsubmissionproplist
portal — Historic. Stored data for old '1.0' version of the Portal; used before the Portal was re-designed.
portal_box_prop — Clustered.
portal_config — Clustered.
portal_typemap
priv_list — Global. Stores list of different admin privileges that users can have.
priv_map
priv_packages
priv_packages_content
procnotify — Global. Table required by DBI::Role for procnotify - the function used to pass a message to all web processes on all clusters.
promo_item
promo_set
qotd — Global. Stores data for the Question of the Day ("Writer's Block") widget.
qotd_imported
random_user_set — Clustered. Stores data about entries for the random user search. On posting an entry (public, to personal journal, and not opted out (using latest_optout option at the console)) a user may end up with a row in this table. The htdocs/random.bml page returns a random user that is both 1) publicly listed in the directory, and 2) updated within the past 24 hours. If a user changes their privacy setting using the console to not be in this table, it will take up to 24 hours for them to be removed from the random.bml listing; a maintenance task builds/cleans the table. The information row is kept for seven days by default. Site administrators can adjust this using the $LJ::RANDOM_USER_PERIOD site variable.
ratelist — Global. Stores the different rate-limited actions a user can make. Used for rate-limiting infrastructure: denying fast failed logins (password brute-forcing), user-to-user messaging, rate-limiting on friend additions, etc.
ratelog — Clustered.
readonly_user — Global. Used by the move user cluster script. Both before and after updating a user's read-only flag we add the user to this table, which is just an index onto users who - might - be in read-only. A maintenance task will periodically clean those and make sure nobody is stranded in read-only, without resorting to a full tablescan of the user table, by checking if users are still locked, removing those that are not from this table, querying the job server (if up) for users that are still locked and unlocking those that can be unlocked.
recbill
recbill_cc
recbill_items
recbill_log
recbill_pendtime
recbill_promo
recentactions — Clustered. Stores a log count of generic actions that have happened, like a post action (which calls LJ::note_recent_action()). A maintenance task moves these logged summaries from the various clusters to the global actionhistory table.
reluser — Global. Stores the special links ("reluser relationships") between accounts, such as community maintainers/moderators. A relationship "type" is a single character. Please see also reluser2.
reluser2 — Clustered. Stores the special links ("reluser relationships") between accounts. Relationship type IDs are defined in the LJ::get_reluser_id function. A relationship "typeid" cannot be a single character. Please see also reluser.
renames
repost2
restore_tasks
s1overrides — Clustered. Stores user S1 style system override customizations. This - clustered - table was used from data version 5. Please see also the global overrides table.
s1style — Clustered. Stores S1 style system user style data. This - clustered - table was used from data version 5. Please see also the global style table.
s1stylecache — Clustered. Stores cached Storable-frozen pre-cleaned style variables.
s1stylemap
s1usercache — Clustered. Stores cached Storable-frozen pre-cleaned S1 user-related style data: overrides and colors.
s2checker
s2compiled — Global. Stores S2 layer data (compdata is not gzipped). Please see also s2compiled2.
s2compiled2 — Clustered. Stores user (not system) S2 layers, and is lazily migrated. This table is indexed by userid, layerid, and contains data that is compressed when it's put in. (Tests show this reduces data size by about 75 percent.) New saves go here. Loads try this table first (unless user is system) and if miss, then try the s2compiled table on the global.
s2info
s2layers
s2source — Global. Stores S2 layer sources. Please see also the newer global InnoDB table s2source_inno.
s2source_inno — Global. Stores new S2 layer sources, and those lazily migrated from s2source. Created to do a live migration from the old MyISAM table (s2source) to this new InnoDB table without requiring downtime.
s2stylelayers — Global. Please see also the clustered s2stylelayers2 table.
s2stylelayers2 — Clustered.
s2styles
sch_exitstatus
sch_funcmap
sch_job
sch_mass_exitstatus
sch_mass_funcmap
sch_mass_job
sch_mass_note
sch_note
sch_reminders
schemacols — Stores the documentation for the individual columns of the database tables.
schematables — Stores the documentation for the database tables.
schools
schools_attended
schools_log
schools_pending
schools_stats
seconddomains
secret_questions — List of system secret questions
secrets — Global. Stores data for a rotating secret value on the server, for auth support. Please see also challenges.
selfpromo
send_email_errors
sessions — Clustered. Stores web sessions data. Optionally tied to IPs and with expiration times. Whenever a session is okayed, expired ones or ones created over 30 days ago are deleted. A live session can't change e-mail address or password. Digest authentication will be required for that, or JavaScript MD5 challenge-response.
sessions_data — Clustered.
shipping
shop_tags
shop_themes
shop_themes_cats
shop_themes_files
shop_userheads
shop_vgift_tagmap
shop_vgifts
site_messages — Global. Stores data for SiteMessages widget (used to post announcements to users).
sms_msg — Clustered. Stores log of SMS message data.
sms_msgack — Clustered. Stores the acknowledgments received for a given message.
sms_msgerror — Clustered. Stores SMS errors if they exist.
sms_msgprop — Clustered.
sms_msgproplist — Global. Stores list of possible metadata for SMS messages. Unlike most other *proplist tables, this one is auto-populated by the LiveJournal application.
sms_msgtext — Clustered. Stores the raw and decoded SMS text content.
sms_promo
sms_quota
smsru
smsru_phones
smsru_vercodes
smsuniqmap — Global. Stores data for mapping remote-party msg unique ids to our userid/msgid tuples; similar to smsusermap.
smsusermap — Stores data for mapping of userid <=> (SMS) number.
spamreports — Global. Stores content marked as spam by users when they delete it, for administrator review. A reported comment, user-to-user message, or community entry is copied into this table, by the LJ::mark_comment_as_spam, LJ::mark_as_spam, or LJ::mark_entry_as_spam function, respectively. The admin tool (/admin/spamreports.bml hinging on siteadmin:spamreports priv) allows spam report viewing: top 10 reported IPs, top 10 reported users (and showing if someone has received a spam warning before), last 10 reports, reports in last 1 hour, 6 hours, and 24 hours; the page supports sorting by open/closed. The 'spamreport_notification' hook exists for optionally notifying people about spamming. A maintenance task cleans out data older than 90 days. Please see also the tempanonips table.
spinvox_msg
splittest
splittest_log
stats
statushistory — Global. Stores an internal log of a user for Support purposes. For example, suspensions and unsuspensions are recorded for the abuse prevention team, and privilege granting/removing is logged. Please see also infohistory.
style — Global. Stores S1 style system user style data. Please see also the clustered s1style table.
subs — Clustered. Stores metadata details about a user's ESN subscriptions. Please see also has_subs.
subscribers2
subscribersleft
subscriptionfilter2
subsprop — Clustered. Stores metadata of a user's ESN subscriptions, from possibilities stored in subsproplist.
subsproplist — Global. Stores list of possible metadata for ESN subscriptions. Unlike most other *proplist tables, this one is auto-populated by the LiveJournal application.
sup_extblocks
sup_sponsor_stats
sup_sponsored_bans
sup_sponsored_user_history
sup_sponsored_users
sup_sponsors
support — Global. Stores data for the Support system. Allows users with the supporthelp priv to see links to support/history.bml, when viewing a Support request, where they can pull up a list of all past requests opened by that user or by that e-mail address.
support_answers — Global. Stores stock answers for Support system. Answers are viewable by those with the "supporthelp" priv, and editable by people who have the ability to grant privileges in their category.
support_answers_backup
support_youreplied — Global. Stores data for which Support tickets a user responded to. Used for speedier querying for the Support system "You Replied" filter.
supportcat — Global. Stores Support system categories.
supportlog
supportlogprop
supportnotify — Global. Stores user subscriptions to Support request categories for e-mail notification of new requests.
supportpoints
supportpointsum — Global. Stores user Support points data. Used for speedier querying for htdocs/support/highscores.bml.
supportprop — Global. Stores metadata on Support requests.
supporttag
supporttagmap
survey_v0_8bit
suspend_history
suspicious_logins
suspicious_logins_api
suspicious_pay_log
syndicated — Global. Stores information on syndicated accounts like feed URI, readership, polling, etc.
synitem
sysban — Global. Stores 'sysban' data - the mechanism for banning users from portions of the site based on certain criteria.
syslog
talk2 — Clustered. Stores metadata about all comments to journal entries. Indexes are all on this table.
talkbackup
talkleft — Clustered. Stores references to where a user has posted comments. Used for comments (user left in other journals) counter on user profile page.
talkleft_xfp — Historic. Global. Stores a user's posts on other clusters, when either 1) that user isn't clustered themselves yet, or 2) we're doing a mass conversion (moveucluster.pl) and don't want to look it up. A maintenance task (clean_caches) moves data from here to talkleft on clusters.
talkprop2 — Clustered. Stores metadata of comments, from possibilities stored in talkproplist.
talkproplist — Global. Stores list of possible metadata for comments.
talktext2 — Clustered. Stores the actual text of comments to journal entries.
talktextbackup
tempanonips — Clustered. Stores IP addresses for spam reports, temporarily, whether the journal in which the anonymous comment was posted in has enabled IP tracking or not. Used with the spamreports table. The LJ::record_anon_comment_ip function gets the anonymous comment IP, and records it here. A maintenance task cleans out IPs after 5 days - so anonymous comments deleted after 5 days are fairly useless, and reports about them are quietly discarded by the comment deletion system.
themecustom
themedata — Global. Stores list of the system colors themes available to users.
themelist — Global. Stores the different S1 style system color schemes.
todo
tododep
todokeyword
tokens_daily_amount
transferinfo
twitter_digest_status
twitter_request_tokens
txtmsg
underage — Global. Stores the data of which accounts are marked as underage.
uniqmap — Global. Stores data for mapping value of unique cookie <=> userid.
urimap — Clustered. Stores data for mapping a named URI permalink - that is: http://somejournal.example.com/this_is_a_named_uri.html (not-yet-implemented), to the respective entry.
user
user_account
user_account_history
user_active_until
user_reginfo_log
user_schools — Clustered.
user_wallet
user_wallet_history
userapps
userapps_items
userapps_payments
userapps_view_html
userapps_views
userbio — Clustered.
userblob — Clustered. Stores blobs (binary large objects) of on-disk data. Blob* files/classes for storing Blobs need to be added either to a local path or a remote Blob server ("remote Blob server" support has since been removed in favor of MogileFS). Notes: blobids aren't necessarily unique between domains; global userpicids may collide with the counter used for the rest. So, the type must be in the key. domain IDs are set up in ljconfig.pl.
userblobcache — Clustered.
usercounter — Stores per-user counters on the global (contrary to the name). These are allocated by the LJ::alloc_user_counter function. Please see also counter.
useridmap — Global. Stores data for mapping userid <=> user(name).
userinterests
userkeywords — Clustered. Stores userpic (userpic2) keywords. Also stores entry keywords (tags), and memory keywords. A site-configurable limit to the number of keywords for each userpic exists; default is 5. This table never gets deleted from, except if the user itself gets deleted. Please see also userpicmap2.
userlog — Clustered. Stores general purpose status log data, such as when an entry is deleted or logging post-by-e-mail activity. The initiator of the event is stored here so we can look back and say, for example: "this person deleted the entry". This works for communities and individual journals, and the actions are logged on the account that lost the entry. The basic format is [ action, actiontarget ].
usermsg — Clustered. Stores metadata about all user-to-user messages. The actual content is stored in usermsgtext.
usermsgbookmarks
usermsgprop — Clustered. Stores metadata of user-to-user messages, from possibilities stored in usermsgproplist.
usermsgproplist — Global. Stores list of possible metadata for user-to-user messages.
usermsgtext — Clustered. Stores the actual text of user-to-user messages.
userpic — Global. Stores userpic metadata. For sites using data version 7 or greater, the clustered userpic2 table is used. Please see also userpicmap and keywords.
userpic2 — Clustered. Stores userpic metadata. The actual userpics are stored in either the database (userpicblob2) or on a blob server. From data version 7 userpics are clustered; the global userpic table is used prior to data version 7. Please see also userpicmap2/userkeywords.
userpicblob2 — Clustered. Stores the actual userpic blobs. Optionally a blob server can be used instead of storing them here in the database.
userpicmap — Global. Stores data for mapping userpic keywords to userpics. Please see also the clustered userpicmap2 table, used from data version 7.
userpicmap2 — Clustered. Stores data for mapping userpic keywords (userkeywords) to userpics (userpic2).
userprop — Global, indexed.
userpropblob — Clustered. Stores user properties greater than 255 bytes.
userproplist — Global. Stores list of possible metadata on users. Allows for having userprops stored globally for indexing; and, by way of the multihomed column, on a cluster as "multihomed userprops", for easy access on user profile pages and such.
userproplite — Global, not indexed.
userproplite2 — Clustered, not indexed.
usersearch_packdata — Global. Stores Directory Search information: userid, a "pack" of information - time of last update, age, journal type, country, state, and city; row modification time, and expiry information.
usersingroups2
usertags — Clustered. Stores metadata of what tags a user has. Please see also userkeywords.
usertrans — Global. Stores user account transitions data (e.g. "free" to "plus", or whatever site-specific capability classes exist).
usertrans_churn
usertrans_sum
userusage — Global. Stores record of when users did certain things.
ver_tags
vertical
vertical2
vertical_comms
vertical_editorials
vertical_entries
vertical_keymap
vertical_keywords
vertical_posts
vertical_rules
vgift_in_cats
vgifts — Stores the history of vgifts sent
vgifts_adnectar
virusgame
virusgame_rating
wallet_blocking
wallet_blocking_history
weekuserusage — Obsolete. It was used to keep track of user activity, such as latest time a user posted in a week, for a given week. Used from data version 3, but ceased to be used later, when the Friends view algorithm was re-designed.
wishlist2
wishrecommendation
zip — Global. ZIP Code table used to validate and auto-complete user-entered location data. More data can be found in the (redundant) table zips, which was imported later.
zips — Global. ZIP Code data for the United States that includes geographic co-ordinates. Only used with an ljcom maintenance script that generates marker files for use in making Xplanet maps. Most of the LJ code uses the zip table instead.