compo.sr  · web viewthe data types used here are our standard composr schema types, which map...

55
Composr Data Dictionary This document shows Composr’s tables, addon-by-addon. Core Composr tables are in the ‘core’ addon. The data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr database, but our types are designed to be intuitive and consistent with how Composr is written, and are also referenced in our API documentation. ‘AUTO’ fields are usually implemented as auto-increment fields, but it depends on the database driver used. We also have SQL dumps of the tables used by each addon that shows what all the foreign keys are in this database. Composr does not use foreign keys in a strict sense internally, because MySQL does not fully support them (only InnoDB does, but that does not support Full-Text search). You may find it useful to import this SQL dump into a blank database, and use a tool such as phpMyAdmin, or MySQL Workbench (free tool, can generate ER diagrams – which we have rendered , but work better interactively), to further understand table relationships. The SQL dump contains one extra table, ‘anything’, which you can think of as a ‘super class’ – it is there to show what attributes might actually be pointing to many different tables (e.g. seo_meta.meta_for_id can point to many tables, and the table pointed to indirectly depends on seo_meta.meta_for_type). ocProducts Ltd. UK registration #05321273 1

Upload: others

Post on 16-Mar-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

Composr Data Dictionary

This document shows Composr’s tables, addon-by-addon.

Core Composr tables are in the ‘core’ addon.

The data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr database, but our types are designed to be intuitive and consistent with how Composr is written, and are also referenced in our API documentation.

‘AUTO’ fields are usually implemented as auto-increment fields, but it depends on the database driver used.

We also have SQL dumps of the tables used by each addon that shows what all the foreign keys are in this database. Composr does not use foreign keys in a strict sense internally, because MySQL does not fully support them (only InnoDB does, but that does not support Full-Text search). You may find it useful to import this SQL dump into a blank database, and use a tool such as phpMyAdmin, or MySQL Workbench (free tool, can generate ER diagrams – which we have rendered, but work better interactively), to further understand table relationships.

The SQL dump contains one extra table, ‘anything’, which you can think of as a ‘super class’ – it is there to show what attributes might actually be pointing to many different tables (e.g. seo_meta.meta_for_id can point to many tables, and the table pointed to indirectly depends on seo_meta.meta_for_type).

ocProducts Ltd. UK registration #05321273 1

Page 2: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

actionlog revisions – used to store old versions of content (any content type that chooses to support revisions)

o AUTO id (Key field)

o AUTO_LINK r_actionlog_id ( → actionlogs.id) (May be NULL)

o ID_TEXT r_category_id

o AUTO_LINK r_moderatorlog_id ( → f_moderator_logs.id) (May be NULL)

o MEMBER r_original_content_owner

o TIME r_original_content_timestamp

o LONG_TEXT r_original_resource_fs_path

o LONG_TEXT r_original_resource_fs_record

o LONG_TEXT r_original_text

o SHORT_TEXT r_original_title

o ID_TEXT r_resource_id

o ID_TEXT r_resource_type

aggregate_types aggregate_type_instances

o TIME add_time

o SHORT_TEXT aggregate_label

o ID_TEXT aggregate_type

o TIME edit_time (May be NULL)

o AUTO id (Key field)

o LONG_TEXT other_parameters

authors authors

o ID_TEXT author (Key field)

o LONG_TRANS__COMCODE description

o MEMBER member_id (May be NULL)

o LONG_TRANS__COMCODE skills

o URLPATH url

awards award_archive

o AUTO_LINK a_type_id ( → award_types.id) (Key field)

o ID_TEXT content_id

o TIME date_and_time (Key field)

Page 3: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o MEMBER member_id

award_types

o ID_TEXT a_content_type

o LONG_TRANS__COMCODE a_description

o BINARY a_hide_awardee

o INTEGER a_points

o SHORT_TRANS a_title

o INTEGER a_update_time_hours

o AUTO id (Key field)

banners banner_clicks

o ID_TEXT c_banner_id

o TIME c_date_and_time

o IP c_ip_address

o MEMBER c_member_id

o ID_TEXT c_source

o AUTO id (Key field)

banner_types

o ID_TEXT id (Key field)

o BINARY t_comcode_inline

o INTEGER t_image_height

o INTEGER t_image_width

o BINARY t_is_textual

o INTEGER t_max_file_size

banners

o TIME add_date

o LONG_TEXT b_direct_code

o SHORT_TEXT b_title_text

o ID_TEXT b_type ( → banner_types.id)

o INTEGER campaign_remaining

o SHORT_TRANS__COMCODE caption

o TIME edit_date (May be NULL)

o TIME expiry_date (May be NULL)

o INTEGER hits_from

o INTEGER hits_to

o URLPATH img_url

o INTEGER importance_modulus

Page 4: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT name (Key field)

o LONG_TEXT notes

o URLPATH site_url

o MEMBER submitter

o SHORT_INTEGER the_type

o BINARY validated

o INTEGER views_from

o INTEGER views_to

banners_types

o ID_TEXT b_type ( → banner_types.id) (Key field)

o ID_TEXT name (Key field)

bookmarks bookmarks

o SHORT_TEXT b_folder

o MEMBER b_owner

o SHORT_TEXT b_page_link

o SHORT_TEXT b_title

o AUTO id (Key field)

calendar calendar_events

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o TIME e_add_date

o LONG_TRANS__COMCODE e_content

o BINARY e_do_timezone_conv

o TIME e_edit_date (May be NULL)

o SHORT_INTEGER e_end_day (May be NULL)

o SHORT_INTEGER e_end_hour (May be NULL)

o SHORT_INTEGER e_end_minute (May be NULL)

o SHORT_INTEGER e_end_month (May be NULL)

o ID_TEXT e_end_monthly_spec_type

o INTEGER e_end_year (May be NULL)

o MEMBER e_member_calendar (May be NULL)

o SHORT_INTEGER e_priority

o ID_TEXT e_recurrence

Page 5: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_INTEGER e_recurrences (May be NULL)

o BINARY e_seg_recurrences

o SHORT_INTEGER e_start_day

o SHORT_INTEGER e_start_hour (May be NULL)

o SHORT_INTEGER e_start_minute (May be NULL)

o SHORT_INTEGER e_start_month

o ID_TEXT e_start_monthly_spec_type

o INTEGER e_start_year

o MEMBER e_submitter

o ID_TEXT e_timezone

o SHORT_TRANS__COMCODE e_title

o AUTO_LINK e_type ( → calendar_types.id)

o INTEGER e_views

o AUTO id (Key field)

o LONG_TEXT notes

o BINARY validated

calendar_interests

o MEMBER i_member_id (Key field)

o AUTO_LINK t_type ( → calendar_types.id) (Key field)

calendar_jobs

o AUTO id (Key field)

o AUTO_LINK j_event_id ( → calendar_events.id)

o MEMBER j_member_id (May be NULL)

o AUTO_LINK j_reminder_id ( → calendar_reminders.id) (May be NULL)

o TIME j_time

calendar_reminders

o AUTO_LINK e_id ( → calendar_events.id)

o AUTO id (Key field)

o MEMBER n_member_id

o INTEGER n_seconds_before

calendar_types

o AUTO id (Key field)

o URLPATH t_external_feed

o SHORT_TEXT t_logo

o SHORT_TRANS__COMCODE t_title

catalogues catalogue_cat_treecache

Page 6: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o AUTO_LINK cc_ancestor_id ( → catalogue_categories.id) (Key field)

o AUTO_LINK cc_id ( → catalogue_categories.id) (Key field)

catalogue_categories

o TIME cc_add_date

o LONG_TRANS__COMCODE cc_description

o INTEGER cc_move_days_higher

o INTEGER cc_move_days_lower

o AUTO_LINK cc_move_target ( → catalogue_categories.id) (May be NULL)

o LONG_TEXT cc_notes

o INTEGER cc_order

o AUTO_LINK cc_parent_id ( → catalogue_categories.id) (May be NULL)

o SHORT_TRANS cc_title

o ID_TEXT c_name ( → catalogues.c_name)

o AUTO id (Key field)

o URLPATH rep_image

catalogue_childcountcache

o AUTO_LINK cc_id ( → catalogue_categories.id) (Key field)

o INTEGER c_num_rec_children

o INTEGER c_num_rec_entries

catalogue_efv_float

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o REAL cv_value (May be NULL)

o AUTO id (Key field)

catalogue_efv_integer

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o INTEGER cv_value (May be NULL)

o AUTO id (Key field)

catalogue_efv_long

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o LONG_TEXT cv_value

o AUTO id (Key field)

catalogue_efv_long_trans

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o LONG_TRANS__COMCODE cv_value

Page 7: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o AUTO id (Key field)

catalogue_efv_short

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o SHORT_TEXT cv_value

o AUTO id (Key field)

catalogue_efv_short_trans

o AUTO_LINK ce_id ( → catalogue_entries.id)

o AUTO_LINK cf_id ( → catalogue_fields.id)

o SHORT_TRANS__COMCODE cv_value

o AUTO id (Key field)

catalogue_entries

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o AUTO_LINK cc_id ( → catalogue_categories.id)

o TIME ce_add_date

o TIME ce_edit_date (May be NULL)

o INTEGER ce_last_moved

o MEMBER ce_submitter

o BINARY ce_validated

o INTEGER ce_views

o INTEGER ce_views_prior

o ID_TEXT c_name ( → catalogues.c_name)

o AUTO id (Key field)

o LONG_TEXT notes

catalogue_entry_linkage

o AUTO_LINK catalogue_entry_id ( → catalogue_entries.id) (Key field)

o ID_TEXT content_id

o ID_TEXT content_type

catalogue_fields

o LONG_TEXT cf_default

o SHORT_INTEGER cf_defines_order

o LONG_TRANS cf_description

o SHORT_TRANS cf_name

o SHORT_TEXT cf_options

o INTEGER cf_order

o BINARY cf_put_in_category

Page 8: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o BINARY cf_put_in_search

o BINARY cf_required

o BINARY cf_searchable

o ID_TEXT cf_type

o BINARY cf_visible

o ID_TEXT c_name ( → catalogues.c_name)

o AUTO id (Key field)

catalogues

o TIME c_add_date

o INTEGER c_default_review_freq (May be NULL)

o LONG_TRANS__COMCODE c_description

o SHORT_INTEGER c_display_type

o BINARY c_ecommerce

o BINARY c_is_tree

o ID_TEXT c_name (Key field)

o LONG_TEXT c_notes

o ID_TEXT c_send_view_reports

o INTEGER c_submit_points

o SHORT_TRANS c_title

chat chat_active

o TIME date_and_time

o AUTO id (Key field)

o MEMBER member_id

o AUTO_LINK room_id ( → chat_rooms.id) (May be NULL)

chat_blocking

o TIME date_and_time

o MEMBER member_blocked (Key field)

o MEMBER member_blocker (Key field)

chat_events

o TIME e_date_and_time

o MEMBER e_member_id

o AUTO_LINK e_room_id ( → chat_rooms.id) (May be NULL)

o ID_TEXT e_type_code

o AUTO id (Key field)

chat_friends

o TIME date_and_time

Page 9: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o MEMBER member_liked (Key field)

o MEMBER member_likes (Key field)

chat_messages

o TIME date_and_time

o SHORT_TEXT font_name

o AUTO id (Key field)

o IP ip_address

o MEMBER member_id

o AUTO_LINK room_id ( → chat_rooms.id)

o BINARY system_message

o SHORT_TEXT text_colour

o LONG_TRANS__COMCODE the_message

chat_rooms

o LONG_TEXT allow_list

o LONG_TEXT allow_list_groups

o LONG_TRANS c_welcome

o LONG_TEXT disallow_list

o LONG_TEXT disallow_list_groups

o AUTO id (Key field)

o BINARY is_im

o LANGUAGE_NAME room_language

o SHORT_TEXT room_name

o INTEGER room_owner (May be NULL)

chat_sound_effects

o ID_TEXT s_effect_id (Key field)

o MEMBER s_member (Key field)

o URLPATH s_url

commandr commandrchat

o BINARY c_incoming

o LONG_TEXT c_message

o TIME c_timestamp

o URLPATH c_url

o AUTO id (Key field)

content_reviews content_reviews

o ID_TEXT auto_action

Page 10: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT content_id (Key field)

o ID_TEXT content_type (Key field)

o BINARY display_review_status

o TIME last_reviewed_time

o TIME next_review_time

o INTEGER review_freq (May be NULL)

o BINARY review_notification_happened

core alternative_ids – different sets of IDs for a database ID, allowing more robust cross-site or label based content

referencing

o ID_TEXT resource_guid

o ID_TEXT resource_id (Key field)

o SHORT_TEXT resource_label

o ID_TEXT resource_moniker

o ID_TEXT resource_resource_fs_hook

o ID_TEXT resource_type (Key field)

attachment_refs – stores references of what content uses what attachments (it allows attachment permissions to work, as it tells Composr what 'owner' content to verify permissions against)

o AUTO_LINK a_id ( → attachments.id)

o AUTO id (Key field)

o ID_TEXT r_referer_id ( → *)

o ID_TEXT r_referer_type

attachments – attachments referenced by Comcode (images, downloads, videos, etc)

o INTEGER a_add_time

o SHORT_TEXT a_description

o INTEGER a_file_size (May be NULL)

o INTEGER a_last_downloaded_time (May be NULL)

o MEMBER a_member_id

o INTEGER a_num_downloads

o SHORT_TEXT a_original_filename

o SHORT_TEXT a_thumb_url

o SHORT_TEXT a_url

o AUTO id (Key field)

autosave – stores unsaved form data in case of browser crashes, called by AJAX

o LONG_TEXT a_key

o MEMBER a_member_id

o TIME a_time

o LONG_TEXT a_value

Page 11: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o AUTO id (Key field)

blocks – a registry of all installed blocks

o ID_TEXT block_author

o ID_TEXT block_hacked_by

o INTEGER block_hack_version (May be NULL)

o ID_TEXT block_name (Key field)

o ID_TEXT block_organisation

o INTEGER block_version

cache – data caching, especially block caching

o ID_TEXT cached_for

o TIME date_and_time

o LONG_TEXT dependencies

o SHORT_TEXT groups

o AUTO id (Key field)

o MINIID_TEXT identifier

o BINARY is_bot (May be NULL)

o LANGUAGE_NAME lang

o BINARY staff_status (May be NULL)

o MEMBER the_member (May be NULL)

o MINIID_TEXT the_theme

o LONG_TEXT the_value

o MINIID_TEXT timezone

cache_on – a registry of what cacheable things are cached by what parameters

o ID_TEXT cached_for (Key field)

o LONG_TEXT cache_on

o INTEGER cache_ttl

o INTEGER special_cache_flags

cached_comcode_pages

o SHORT_TRANS cc_page_title (May be NULL)

o LONG_TRANS__COMCODE string_index

o ID_TEXT the_page (Key field)

o ID_TEXT the_theme (Key field)

o ID_TEXT the_zone ( → zones.zone_name) (Key field)

captchas – stores CAPTCHA image expectations, so Composr can check what they entered against what they were asked to enter

o ID_TEXT si_code

o ID_TEXT si_session_id (Key field)

o TIME si_time

comcode_pages

Page 12: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o TIME p_add_date

o TIME p_edit_date (May be NULL)

o INTEGER p_order

o ID_TEXT p_parent_page

o BINARY p_show_as_edit

o MEMBER p_submitter

o BINARY p_validated

o ID_TEXT the_page (Key field)

o ID_TEXT the_zone (Key field)

config – all the configuration settings that have been saved

o ID_TEXT c_name (Key field)

o BINARY c_needs_dereference

o BINARY c_set

o LONG_TEXT c_value

o LONG_TRANS c_value_trans (May be NULL)

content_privacy

o ID_TEXT content_id (Key field)

o ID_TEXT content_type (Key field)

o BINARY friend_view

o BINARY guest_view

o BINARY member_view

content_privacy__members – sets content privacy

o ID_TEXT content_id (Key field)

o ID_TEXT content_type (Key field)

o MEMBER member_id (Key field)

content_regions – sets the regions content may be viewed from

o ID_TEXT content_id (Key field)

o ID_TEXT content_type (Key field)

o ID_TEXT region (Key field)

cron_caching_requests

o ID_TEXT c_codename

o SHORT_TEXT c_groups

o BINARY c_is_bot (May be NULL)

o LANGUAGE_NAME c_lang

o LONG_TEXT c_map

o MEMBER c_member (May be NULL)

o BINARY c_staff_status (May be NULL)

o BINARY c_store_as_tempcode

Page 13: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT c_theme

o MINIID_TEXT c_timezone

o AUTO id (Key field)

digestives_consumed

o INTEGER c_frequency (Key field)

o MEMBER c_member_id (Key field)

o TIME c_time

digestives_tin

o SHORT_TEXT d_code_category

o TIME d_date_and_time

o INTEGER d_frequency

o MEMBER d_from_member_id (May be NULL)

o LONG_TRANS__COMCODE d_message

o ID_TEXT d_notification_code

o BINARY d_no_cc

o SHORT_INTEGER d_priority

o BINARY d_read

o LONG_TEXT d_subject

o MEMBER d_to_member_id

o AUTO id (Key field)

edit_pings – used to stop people editing the same thing at the same time (AJAX)

o AUTO id (Key field)

o ID_TEXT the_id

o MEMBER the_member

o ID_TEXT the_page

o TIME the_time

o ID_TEXT the_type

email_bounces

o LONG_TEXT b_body

o SHORT_TEXT b_email_address

o SHORT_TEXT b_subject

o TIME b_time

o AUTO id (Key field)

f_group_member_timeouts

o GROUP group_id (Key field)

o MEMBER member_id (Key field)

o TIME timeout

failedlogins – a log of all failed logins

Page 14: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o TIME date_and_time

o ID_TEXT failed_account

o AUTO id (Key field)

o IP ip

feature_lifetime_monitor

o ID_TEXT block_cache_id (Key field)

o ID_TEXT content_id (Key field)

o TIME last_update

o BINARY running_now

o INTEGER run_period

group_category_access – defines what groups may access what categories

o ID_TEXT category_name ( → *) (Key field)

o GROUP group_id (Key field)

o ID_TEXT module_the_name (Key field)

group_page_access – defines what groups may access what pages

o GROUP group_id (Key field)

o ID_TEXT page_name (Key field)

o ID_TEXT zone_name ( → zones.zone_name) (Key field)

group_privileges – defines what groups have what privileges

o ID_TEXT category_name ( → *) (Key field)

o INTEGER group_id (Key field)

o ID_TEXT module_the_name (Key field)

o ID_TEXT privilege ( → privilege_list.the_name) (Key field)

o ID_TEXT the_page ( → modules.module_the_name) (Key field)

o BINARY the_value

group_zone_access – defines what groups may access what zones

o GROUP group_id (Key field)

o ID_TEXT zone_name ( → zones.zone_name) (Key field)

https_pages – lists pages that the webmaster has decided need to run over SSL

o ID_TEXT https_page_name (Key field)

incoming_uploads – temporary storage of uploaded files, before main form submission

o AUTO id (Key field)

o TIME i_date_and_time

o URLPATH i_orig_filename

o SHORT_TEXT i_save_url

o MEMBER i_submitter

link_tracker – outgoing click tracking (not really used much)

o TIME c_date_and_time

o IP c_ip_address

Page 15: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o MEMBER c_member_id

o URLPATH c_url

o AUTO id (Key field)

logged_mail_messages – logged emails (so you can check incorrect emails aren't going out) / email queuing

o AUTO id (Key field)

o MEMBER m_as

o BINARY m_as_admin

o LONG_TEXT m_attachments

o TIME m_date_and_time

o LONG_TEXT m_extra_bcc_addresses

o LONG_TEXT m_extra_cc_addresses

o SHORT_TEXT m_from_email

o SHORT_TEXT m_from_name

o BINARY m_in_html

o TIME m_join_time (May be NULL)

o MEMBER m_member_id

o LONG_TEXT m_message

o BINARY m_no_cc

o SHORT_INTEGER m_priority

o BINARY m_queued

o LONG_TEXT m_subject

o ID_TEXT m_template

o LONG_TEXT m_to_email

o LONG_TEXT m_to_name

o LONG_TEXT m_url

member_category_access – defines what members may access what categories (rarely used, no admin UI)

o TIME active_until (May be NULL)

o ID_TEXT category_name ( → *) (Key field)

o MEMBER member_id (Key field)

o ID_TEXT module_the_name (Key field)

member_page_access – defines what members may access what pages (rarely used, no admin UI)

o TIME active_until (May be NULL)

o MEMBER member_id (Key field)

o ID_TEXT page_name ( → modules.module_the_name) (Key field)

o ID_TEXT zone_name ( → zones.zone_name) (Key field)

member_privileges – defines what members have what privileges (rarely used, no admin UI)

o TIME active_until (May be NULL)

o ID_TEXT category_name ( → *) (Key field)

Page 16: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o INTEGER member_id (Key field)

o ID_TEXT module_the_name (Key field)

o ID_TEXT privilege ( → privilege_list.the_name) (Key field)

o ID_TEXT the_page ( → modules.module_the_name) (Key field)

o BINARY the_value

member_tracking – tracks the locations of online users

o ID_TEXT mt_cache_username

o ID_TEXT mt_id (Key field)

o MEMBER mt_member_id (Key field)

o ID_TEXT mt_page (Key field)

o TIME mt_time (Key field)

o ID_TEXT mt_type (Key field)

member_zone_access – defines what members may access what zones (rarely used, no admin UI)

o TIME active_until (May be NULL)

o MEMBER member_id (Key field)

o ID_TEXT zone_name ( → zones.zone_name) (Key field)

menu_items – stores all the items shown on menus (except auto-generated ones)

o AUTO id (Key field)

o SHORT_TRANS__COMCODE i_caption

o SHORT_TRANS__COMCODE i_caption_long

o BINARY i_check_permissions

o BINARY i_expanded

o SHORT_INTEGER i_include_sitemap

o ID_TEXT i_menu

o BINARY i_new_window

o INTEGER i_order

o ID_TEXT i_page_only

o AUTO_LINK i_parent ( → menu_items.id) (May be NULL)

o ID_TEXT i_theme_img_code

o SHORT_TEXT i_url

messages_to_render – stores messages that have been queued up for display on a members browser (e.g. if they have just been redirected after completing something, so a status message will be queued for display after they've been redirected)

o AUTO id (Key field)

o LONG_TEXT r_message

o ID_TEXT r_session_id ( → sessions.the_session)

o TIME r_time

o ID_TEXT r_type

modules – registry of all installed modules

Page 17: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT module_author

o ID_TEXT module_hacked_by

o INTEGER module_hack_version (May be NULL)

o ID_TEXT module_organisation

o ID_TEXT module_the_name (Key field)

o INTEGER module_version

notifications_enabled – what notifications members receive

o AUTO id (Key field)

o SHORT_TEXT l_code_category ( → *)

o MEMBER l_member_id

o ID_TEXT l_notification_code

o INTEGER l_setting

privilege_list – a list of all the privileges available (aka privileges)

o ID_TEXT p_section

o BINARY the_default (Key field)

o ID_TEXT the_name (Key field)

rating – stores ratings for all kinds of content (rating_for_type determines what kind of content, rating_for_id determines what ID of content within that type)

o AUTO id (Key field)

o SHORT_INTEGER rating

o ID_TEXT rating_for_id ( → modules.module_the_name)

o ID_TEXT rating_for_type

o IP rating_ip

o MEMBER rating_member

o TIME rating_time

review_supplement – stores reviews for all kinds of content

o AUTO_LINK r_post_id ( → f_posts.id) (Key field)

o SHORT_INTEGER r_rating

o ID_TEXT r_rating_for_id ( → modules.module_the_name)

o ID_TEXT r_rating_for_type

o ID_TEXT r_rating_type (Key field)

o AUTO_LINK r_topic_id ( → f_topics.id)

seo_meta – stores meta descriptions for all kinds of content

o AUTO id (Key field)

o LONG_TRANS meta_description

o ID_TEXT meta_for_id ( → *)

o ID_TEXT meta_for_type

seo_meta_keywords – stores meta keywords for all kinds of content

o AUTO id (Key field)

Page 18: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT meta_for_id

o ID_TEXT meta_for_type

o SHORT_TRANS meta_keyword

sessions – stores user sessions, for guests and members (session ID's are treated with high security)

o SHORT_TEXT cache_username

o IP ip

o TIME last_activity

o MEMBER member_id

o BINARY session_confirmed

o BINARY session_invisible

o ID_TEXT the_id

o ID_TEXT the_page

o ID_TEXT the_session (Key field)

o SHORT_TEXT the_title

o ID_TEXT the_type

o ID_TEXT the_zone

sitemap_cache – a cache of all addressable sitemap nodes for building out the full XML sitemaps across multiple files iteratively, which is extremely intensive on large sites

o TIME add_date (May be NULL)

o TIME edit_date (May be NULL)

o BINARY guest_access

o BINARY is_deleted

o TIME last_updated

o SHORT_TEXT page_link (Key field)

o REAL priority

o ID_TEXT refreshfreq

o INTEGER set_number

task_queue

o AUTO id (Key field)

o LONG_TEXT t_args

o ID_TEXT t_hook

o BINARY t_locked

o MEMBER t_member_id

o ID_TEXT t_secure_ref

o BINARY t_send_notification

o SHORT_TEXT t_title

temp_block_permissions

o AUTO id (Key field)

o LONG_TEXT p_block_constraints

Page 19: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT p_session_id ( → sessions.the_session)

o TIME p_time

trackbacks – stores trackbacks for all kinds of content

o AUTO id (Key field)

o LONG_TEXT trackback_excerpt

o ID_TEXT trackback_for_id ( → *)

o ID_TEXT trackback_for_type

o IP trackback_ip

o SHORT_TEXT trackback_name

o TIME trackback_time

o SHORT_TEXT trackback_title

o SHORT_TEXT trackback_url

translate – very important table, stores most of the text; this table exists to internationalise content and also to store compiled Comcode

o BINARY broken

o AUTO id (Key field)

o SHORT_INTEGER importance_level

o LANGUAGE_NAME language (Key field)

o MEMBER source_user

o LONG_TEXT text_original

o LONG_TEXT text_parsed

tutorial_links – used by the Composr documentation, don't worry about this table

o ID_TEXT the_name (Key field)

o LONG_TEXT the_value

unbannable_ip

o IP ip (Key field)

o SHORT_TEXT note

url_id_monikers – stores search-engine-friendly URL codes for all kinds of content (we call these "monikers")

o AUTO id (Key field)

o BINARY m_deprecated

o BINARY m_manually_chosen

o SHORT_TEXT m_moniker

o SHORT_TEXT m_moniker_reversed

o ID_TEXT m_resource_id ( → *)

o ID_TEXT m_resource_page

o ID_TEXT m_resource_type

url_title_cache – stores the HTML titles for URLs, used in particular by the Comcode parser when it auto-detects links, and the media rendering system

o AUTO id (Key field)

Page 20: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o LONG_TEXT t_description

o URLPATH t_image_url

o URLPATH t_json_discovery

o LONG_TEXT t_keywords

o LONG_TEXT t_meta_title

o ID_TEXT t_mime_type

o SHORT_TEXT t_title

o URLPATH t_url

o URLPATH t_xml_discovery

urls_checked – stores whether URLs exists, may be used by any system within Composr

o AUTO id (Key field)

o LONG_TEXT url

o TIME url_check_time

o BINARY url_exists

values – arbitrary store of data values (mapping of keys to values)

o TIME date_and_time

o ID_TEXT the_name (Key field)

o SHORT_TEXT the_value

values_elective – arbitrary store of lengthy/elective data values (mapping of keys to values)

o TIME date_and_time

o ID_TEXT the_name (Key field)

o LONG_TEXT the_value

webstandards_checked_once – this is used by the inbuilt XHTML checker to know what markup it has already checked, so it doesn't waste a lot of time re-checking the same stuff; it uses a hash-signature-check so it doesn't need to store all data in the table

o SHORT_TEXT hash (Key field)

zones – details of all zones on the website

o ID_TEXT zone_default_page

o SHORT_TRANS zone_header_text

o ID_TEXT zone_name (Key field)

o BINARY zone_require_session

o ID_TEXT zone_theme

o SHORT_TRANS zone_title

core_addon_management addons

o SHORT_TEXT addon_author

o SHORT_TEXT addon_category

o SHORT_TEXT addon_copyright_attribution

Page 21: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o LONG_TEXT addon_description

o TIME addon_install_time

o SHORT_TEXT addon_licence

o SHORT_TEXT addon_name (Key field)

o SHORT_TEXT addon_organisation

o SHORT_TEXT addon_version

addons_dependencies

o SHORT_TEXT addon_name

o SHORT_TEXT addon_name_dependant_upon

o BINARY addon_name_incompatibility

o AUTO id (Key field)

addons_files

o SHORT_TEXT addon_name

o SHORT_TEXT filename

o AUTO id (Key field)

core_adminzone_dashboard actionlogs – stores logs of actions performed on the website

o TIME date_and_time

o AUTO id (Key field)

o IP ip

o MEMBER member_id

o ID_TEXT param_a

o SHORT_TEXT param_b

o ID_TEXT the_type

staff_checklist_cus_tasks

o TIME add_date

o AUTO id (Key field)

o ID_TEXT recur_every

o INTEGER recur_interval

o TIME task_is_done (May be NULL)

o SHORT_TEXT task_title

staff_links

o AUTO id (Key field)

o URLPATH link

o LONG_TEXT link_desc

o SHORT_TEXT link_title

staff_tips_dismissed – stores what webmaster tips (Admin Zone front page) have been read so far

o MEMBER t_member (Key field)

Page 22: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT t_tip (Key field)

staff_website_monitoring

o AUTO id (Key field)

o SHORT_TEXT site_name

o URLPATH site_url

core_cns f_custom_fields

o LONG_TEXT cf_default

o SHORT_TRANS cf_description

o BINARY cf_encrypted

o BINARY cf_locked

o SHORT_TRANS cf_name

o LONG_TEXT cf_only_group

o SHORT_TEXT cf_options

o INTEGER cf_order

o BINARY cf_owner_set

o BINARY cf_owner_view

o BINARY cf_public_view

o BINARY cf_required

o BINARY cf_show_in_posts

o BINARY cf_show_in_post_previews

o BINARY cf_show_on_join_form

o ID_TEXT cf_type

o AUTO id (Key field)

f_emoticons

o ID_TEXT e_code (Key field)

o BINARY e_is_special

o INTEGER e_relevance_level

o SHORT_TEXT e_theme_img_code

o BINARY e_use_topics

f_forum_groupings

o LONG_TEXT c_description

o BINARY c_expanded_by_default

o SHORT_TEXT c_title

o AUTO id (Key field)

f_forum_intro_ip

o AUTO_LINK i_forum_id ( → f_forums.id) (Key field)

Page 23: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o IP i_ip (Key field)

f_forum_intro_member

o AUTO_LINK i_forum_id ( → f_forums.id) (Key field)

o MEMBER i_member_id (Key field)

f_forums

o BINARY f_allows_anonymous_posts

o AUTO_LINK f_cache_last_forum_id ( → f_forums.id) (May be NULL)

o MEMBER f_cache_last_member_id (May be NULL)

o TIME f_cache_last_time (May be NULL)

o SHORT_TEXT f_cache_last_title

o AUTO_LINK f_cache_last_topic_id ( → f_topics.id) (May be NULL)

o SHORT_TEXT f_cache_last_username

o INTEGER f_cache_num_posts

o INTEGER f_cache_num_topics

o LONG_TRANS__COMCODE f_description

o AUTO_LINK f_forum_grouping_id ( → f_forum_groupings.id) (May be NULL)

o SHORT_TEXT f_intro_answer

o LONG_TRANS__COMCODE f_intro_question

o BINARY f_is_threaded

o SHORT_TEXT f_name

o ID_TEXT f_order

o BINARY f_order_sub_alpha

o AUTO_LINK f_parent_forum ( → f_forums.id) (May be NULL)

o INTEGER f_position

o BINARY f_post_count_increment

o SHORT_TEXT f_redirection

o AUTO id (Key field)

f_group_join_log

o AUTO id (Key field)

o TIME join_time

o MEMBER member_id

o AUTO_LINK usergroup_id ( → f_groups.id) (May be NULL)

f_group_members

o GROUP gm_group_id (Key field)

o MEMBER gm_member_id (Key field)

o BINARY gm_validated

f_groups

o BINARY g_enquire_on_new_ips

Page 24: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o INTEGER g_flood_control_access_secs

o INTEGER g_flood_control_submit_secs

o INTEGER g_gift_points_base

o INTEGER g_gift_points_per_day

o MEMBER g_group_leader (May be NULL)

o BINARY g_hidden

o BINARY g_is_default

o BINARY g_is_presented_at_install

o BINARY g_is_private_club

o BINARY g_is_super_admin

o BINARY g_is_super_moderator

o INTEGER g_max_attachments_per_post

o INTEGER g_max_avatar_height

o INTEGER g_max_avatar_width

o INTEGER g_max_daily_upload_mb

o INTEGER g_max_post_length_comcode

o INTEGER g_max_sig_length_comcode

o SHORT_TRANS g_name

o BINARY g_open_membership

o INTEGER g_order

o GROUP g_promotion_target (May be NULL)

o INTEGER g_promotion_threshold (May be NULL)

o ID_TEXT g_rank_image

o BINARY g_rank_image_pri_only

o SHORT_TRANS g_title

o AUTO id (Key field)

f_invites

o AUTO id (Key field)

o SHORT_TEXT i_email_address

o MEMBER i_inviter

o BINARY i_taken

o TIME i_time

f_member_cpf_perms

o AUTO_LINK field_id ( → f_custom_fields.id) (Key field)

o BINARY friend_view

o SHORT_TEXT group_view

o BINARY guest_view

o MEMBER member_id (Key field)

Page 25: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o BINARY member_view

f_member_custom_fields

o LONG_TRANS__COMCODE field_1

o INTEGER field_10 (May be NULL)

o INTEGER field_11 (May be NULL)

o SHORT_TEXT field_12

o SHORT_TEXT field_13

o SHORT_TEXT field_14

o SHORT_TEXT field_15

o LONG_TEXT field_16

o INTEGER field_17 (May be NULL)

o INTEGER field_18 (May be NULL)

o INTEGER field_19 (May be NULL)

o SHORT_TEXT field_2

o INTEGER field_20 (May be NULL)

o INTEGER field_21 (May be NULL)

o INTEGER field_22 (May be NULL)

o INTEGER field_23 (May be NULL)

o LONG_TEXT field_24

o SHORT_TEXT field_25

o LONG_TEXT field_26

o INTEGER field_27 (May be NULL)

o SHORT_TEXT field_28

o SHORT_TEXT field_29

o SHORT_TEXT field_3

o SHORT_TEXT field_30

o SHORT_TEXT field_31

o SHORT_TEXT field_32

o SHORT_TEXT field_33

o INTEGER field_34 (May be NULL)

o REAL field_35 (May be NULL)

o REAL field_36 (May be NULL)

o LONG_TEXT field_37

o SHORT_TEXT field_38

o SHORT_TEXT field_39

o SHORT_TEXT field_4

o SHORT_TEXT field_40

o SHORT_TEXT field_41

Page 26: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o LONG_TEXT field_42

o SHORT_TEXT field_43

o SHORT_TEXT field_44

o SHORT_TEXT field_45

o SHORT_TEXT field_5

o LONG_TRANS__COMCODE field_6

o SHORT_TEXT field_7

o SHORT_TEXT field_8

o LONG_TRANS__COMCODE field_9

o MEMBER mf_member_id (Key field)

f_member_known_login_ips

o IP i_ip (Key field)

o MEMBER i_member_id (Key field)

o SHORT_TEXT i_val_code

f_members

o AUTO id (Key field)

o BINARY m_allow_emails

o BINARY m_allow_emails_from_staff

o BINARY m_auto_mark_read

o BINARY m_auto_monitor_contrib_content

o URLPATH m_avatar_url

o INTEGER m_cache_num_posts

o INTEGER m_cache_warnings

o SHORT_INTEGER m_dob_day (May be NULL)

o SHORT_INTEGER m_dob_month (May be NULL)

o INTEGER m_dob_year (May be NULL)

o SHORT_TEXT m_email_address

o BINARY m_highlighted_name

o IP m_ip_address

o BINARY m_is_perm_banned

o TIME m_join_time

o ID_TEXT m_language

o TIME m_last_submit_time

o TIME m_last_visit_time

o INTEGER m_max_email_attach_size_mb

o TIME m_on_probation_until (May be NULL)

o SHORT_TEXT m_password_change_code

o ID_TEXT m_password_compat_scheme

Page 27: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT m_pass_hash_salted

o SHORT_TEXT m_pass_salt

o URLPATH m_photo_thumb_url

o URLPATH m_photo_url

o BINARY m_preview_posts

o GROUP m_primary_group

o UINTEGER m_profile_views

o SHORT_TEXT m_pt_allow

o LONG_TRANS__COMCODE m_pt_rules_text

o BINARY m_reveal_age

o LONG_TRANS__COMCODE m_signature

o ID_TEXT m_theme

o SHORT_TEXT m_timezone_offset

o SHORT_TEXT m_title

o UINTEGER m_total_sessions

o ID_TEXT m_username

o BINARY m_validated

o SHORT_TEXT m_validated_email_confirm_code

o BINARY m_views_signatures

f_moderator_logs

o AUTO id (Key field)

o MEMBER l_by

o TIME l_date_and_time

o SHORT_TEXT l_param_a

o SHORT_TEXT l_param_b

o LONG_TEXT l_reason

o ID_TEXT l_the_type

f_multi_moderations

o AUTO id (Key field)

o SHORT_TEXT mm_forum_multi_code

o AUTO_LINK mm_move_to ( → f_forums.id) (May be NULL)

o SHORT_TRANS mm_name

o BINARY mm_open_state (May be NULL)

o BINARY mm_pin_state (May be NULL)

o LONG_TEXT mm_post_text

o BINARY mm_sink_state (May be NULL)

o SHORT_TEXT mm_title_suffix

f_password_history

Page 28: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o AUTO id (Key field)

o SHORT_TEXT p_hash_salted

o MEMBER p_member_id

o SHORT_TEXT p_salt

o TIME p_time

f_poll_answers

o AUTO id (Key field)

o SHORT_TEXT pa_answer

o INTEGER pa_cache_num_votes

o AUTO_LINK pa_poll_id ( → f_polls.id)

f_poll_votes

o AUTO id (Key field)

o AUTO_LINK pv_answer_id ( → f_poll_answers.id)

o IP pv_ip

o MEMBER pv_member_id

o AUTO_LINK pv_poll_id ( → f_polls.id)

f_polls

o AUTO id (Key field)

o INTEGER po_cache_total_votes

o BINARY po_is_open

o BINARY po_is_private

o INTEGER po_maximum_selections

o INTEGER po_minimum_selections

o SHORT_TEXT po_question

o BINARY po_requires_reply

f_post_templates

o AUTO id (Key field)

o SHORT_TEXT t_forum_multi_code

o LONG_TEXT t_text

o SHORT_TEXT t_title

o BINARY t_use_default_forums

f_posts

o AUTO id (Key field)

o AUTO_LINK p_cache_forum_id ( → f_forums.id) (May be NULL)

o MEMBER p_intended_solely_for (May be NULL)

o IP p_ip_address

o BINARY p_is_emphasised

o MEMBER p_last_edit_by (May be NULL)

Page 29: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o TIME p_last_edit_time (May be NULL)

o AUTO_LINK p_parent_id ( → f_posts.id) (May be NULL)

o LONG_TRANS__COMCODE p_post

o MEMBER p_poster

o ID_TEXT p_poster_name_if_guest

o BINARY p_skip_sig

o TIME p_time

o SHORT_TEXT p_title

o AUTO_LINK p_topic_id ( → f_topics.id)

o BINARY p_validated

f_read_logs

o MEMBER l_member_id (Key field)

o TIME l_time

o AUTO_LINK l_topic_id ( → f_topics.id) (Key field)

f_saved_warnings

o LONG_TEXT s_explanation

o LONG_TEXT s_message

o SHORT_TEXT s_title (Key field)

f_special_pt_access

o MEMBER s_member_id (Key field)

o AUTO_LINK s_topic_id ( → f_topics.id) (Key field)

f_topics

o AUTO id (Key field)

o MEMBER t_cache_first_member_id (May be NULL)

o LONG_TRANS__COMCODE t_cache_first_post (May be NULL)

o AUTO_LINK t_cache_first_post_id ( → f_posts.id) (May be NULL)

o TIME t_cache_first_time (May be NULL)

o SHORT_TEXT t_cache_first_title

o ID_TEXT t_cache_first_username

o MEMBER t_cache_last_member_id (May be NULL)

o AUTO_LINK t_cache_last_post_id ( → f_posts.id) (May be NULL)

o TIME t_cache_last_time (May be NULL)

o SHORT_TEXT t_cache_last_title

o ID_TEXT t_cache_last_username

o INTEGER t_cache_num_posts

o BINARY t_cascading

o SHORT_TEXT t_description

o SHORT_TEXT t_description_link

Page 30: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT t_emoticon

o AUTO_LINK t_forum_id ( → f_forums.id) (May be NULL)

o BINARY t_is_open

o INTEGER t_num_views

o BINARY t_pinned

o AUTO_LINK t_poll_id ( → f_polls.id) (May be NULL)

o MEMBER t_pt_from (May be NULL)

o SHORT_TEXT t_pt_from_category

o MEMBER t_pt_to (May be NULL)

o SHORT_TEXT t_pt_to_category

o BINARY t_sunk

o BINARY t_validated

f_warnings

o AUTO id (Key field)

o IP p_banned_ip

o BINARY p_banned_member

o GROUP p_changed_usergroup_from (May be NULL)

o INTEGER p_charged_points

o INTEGER p_probation

o AUTO_LINK p_silence_from_forum ( → f_forums.id) (May be NULL)

o AUTO_LINK p_silence_from_topic ( → f_topics.id) (May be NULL)

o MEMBER w_by

o LONG_TEXT w_explanation

o BINARY w_is_warning

o MEMBER w_member_id

o TIME w_time

core_notifications notification_lockdown

o ID_TEXT l_notification_code (Key field)

o INTEGER l_setting

core_permission_management match_key_messages

o AUTO id (Key field)

o SHORT_TEXT k_match_key

o LONG_TRANS__COMCODE k_message

core_themeing

Page 31: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

theme_images

o SHORT_TEXT id (Key field)

o LANGUAGE_NAME lang (Key field)

o URLPATH path

o MINIID_TEXT theme (Key field)

custom_comcode custom_comcode

o BINARY tag_block_tag

o BINARY tag_dangerous_tag

o SHORT_TRANS tag_description

o BINARY tag_enabled

o LONG_TEXT tag_example

o SHORT_TEXT tag_parameters

o LONG_TEXT tag_replace

o ID_TEXT tag_tag (Key field)

o BINARY tag_textual_tag

o SHORT_TRANS tag_title

downloads download_categories

o TIME add_date

o SHORT_TRANS category

o LONG_TRANS__COMCODE description

o AUTO id (Key field)

o LONG_TEXT notes

o AUTO_LINK parent_id ( → download_categories.id) (May be NULL)

o URLPATH rep_image

download_downloads

o LONG_TRANS__COMCODE additional_details

o TIME add_date

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o ID_TEXT author

o AUTO_LINK category_id ( → download_categories.id)

o INTEGER default_pic

o LONG_TRANS__COMCODE description

Page 32: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o INTEGER download_cost

o LONG_TEXT download_data_mash

o AUTO_LINK download_licence ( → download_licences.id) (May be NULL)

o BINARY download_submitter_gets_points

o INTEGER download_views

o TIME edit_date (May be NULL)

o INTEGER file_size (May be NULL)

o AUTO id (Key field)

o SHORT_TRANS name

o LONG_TEXT notes

o INTEGER num_downloads

o SHORT_TEXT original_filename

o AUTO_LINK out_mode_id ( → download_downloads.id) (May be NULL)

o URLPATH rep_image

o MEMBER submitter

o URLPATH url

o URLPATH url_redirect

o BINARY validated

download_licences

o AUTO id (Key field)

o LONG_TEXT l_text

o SHORT_TEXT l_title

download_logging

o TIME date_and_time

o AUTO_LINK id ( → download_downloads.id) (Key field)

o IP ip

o MEMBER member_id (Key field)

ecommerce f_usergroup_sub_mails

o AUTO id (Key field)

o LONG_TRANS m_body

o ID_TEXT m_ref_point

o INTEGER m_ref_point_offset

o SHORT_TRANS m_subject

o AUTO_LINK m_usergroup_sub_id ( → f_usergroup_subs.id)

f_usergroup_subs

o AUTO id (Key field)

Page 33: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o BINARY s_auto_recur

o SHORT_TEXT s_cost

o LONG_TRANS__COMCODE s_description

o BINARY s_enabled

o GROUP s_group_id

o INTEGER s_length

o SHORT_TEXT s_length_units

o LONG_TRANS s_mail_end

o LONG_TRANS s_mail_start

o LONG_TRANS s_mail_uhoh

o SHORT_TRANS s_title

o BINARY s_uses_primary

invoices

o AUTO id (Key field)

o SHORT_TEXT i_amount

o MEMBER i_member_id

o LONG_TEXT i_note

o SHORT_TEXT i_special

o ID_TEXT i_state

o TIME i_time

o ID_TEXT i_type_code

subscriptions

o AUTO id (Key field)

o SHORT_TEXT s_amount

o SHORT_TEXT s_auto_fund_key

o ID_TEXT s_auto_fund_source

o INTEGER s_length

o SHORT_TEXT s_length_units

o MEMBER s_member_id

o ID_TEXT s_purchase_id

o ID_TEXT s_state

o TIME s_time

o ID_TEXT s_type_code

o ID_TEXT s_via

trans_expecting

o SHORT_TEXT e_amount

o ID_TEXT e_currency

o IP e_ip_address

Page 34: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT e_item_name

o INTEGER e_length (May be NULL)

o ID_TEXT e_length_units

o MEMBER e_member_id

o ID_TEXT e_purchase_id

o ID_TEXT e_session_id

o TIME e_time

o ID_TEXT id (Key field)

transactions

o ID_TEXT id (Key field)

o SHORT_TEXT t_amount

o ID_TEXT t_currency

o LONG_TEXT t_memo

o ID_TEXT t_parent_txn_id

o SHORT_TEXT t_pending_reason

o ID_TEXT t_purchase_id

o SHORT_TEXT t_reason

o SHORT_TEXT t_status

o TIME t_time (Key field)

o ID_TEXT t_type_code

o ID_TEXT t_via

filedump filedump

o SHORT_TRANS description

o AUTO id (Key field)

o ID_TEXT name

o URLPATH path

o MEMBER the_member

galleries galleries

o BINARY accept_images

o BINARY accept_videos

o TIME add_date

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o LONG_TRANS__COMCODE description

Page 35: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o BINARY flow_mode_interface

o SHORT_TRANS__COMCODE fullname

o INTEGER gallery_views

o AUTO_LINK g_owner ( → f_members.id) (May be NULL)

o BINARY is_member_synched

o ID_TEXT name (Key field)

o LONG_TEXT notes

o ID_TEXT parent_id ( → galleries.name)

o URLPATH rep_image

o URLPATH watermark_bottom_left

o URLPATH watermark_bottom_right

o URLPATH watermark_top_left

o URLPATH watermark_top_right

images

o TIME add_date

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o ID_TEXT cat ( → galleries.name)

o LONG_TRANS__COMCODE description

o TIME edit_date (May be NULL)

o AUTO id (Key field)

o INTEGER image_views

o LONG_TEXT notes

o MEMBER submitter

o URLPATH thumb_url

o SHORT_TRANS title

o URLPATH url

o BINARY validated

video_transcoding

o LONG_TEXT t_error

o ID_TEXT t_height_field

o ID_TEXT t_id (Key field)

o AUTO_LINK t_local_id ( → videos.id) (May be NULL)

o ID_TEXT t_local_id_field

o ID_TEXT t_orig_filename_field

o ID_TEXT t_output_filename

o ID_TEXT t_table

Page 36: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o URLPATH t_url

o ID_TEXT t_url_field

o ID_TEXT t_width_field

videos

o TIME add_date

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o ID_TEXT cat ( → galleries.name)

o LONG_TRANS__COMCODE description

o TIME edit_date (May be NULL)

o AUTO id (Key field)

o LONG_TEXT notes

o MEMBER submitter

o URLPATH thumb_url

o SHORT_TRANS title

o URLPATH url

o BINARY validated

o INTEGER video_height

o INTEGER video_length

o INTEGER video_views

o INTEGER video_width

import import_id_remap

o AUTO_LINK id_new ( → *)

o ID_TEXT id_old ( → *) (Key field)

o ID_TEXT id_session (Key field)

o ID_TEXT id_type (Key field)

import_parts_done

o AUTO id (Key field)

o SHORT_TEXT imp_id

o ID_TEXT imp_session

import_session

o ID_TEXT imp_db_host

o ID_TEXT imp_db_name

o ID_TEXT imp_db_table_prefix

o ID_TEXT imp_db_user

Page 37: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT imp_hook

o SHORT_TEXT imp_old_base_dir

o INTEGER imp_refresh_time

o ID_TEXT imp_session (Key field)

news news

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o ID_TEXT author

o TIME date_and_time

o TIME edit_date (May be NULL)

o AUTO id (Key field)

o LONG_TRANS__COMCODE news

o LONG_TRANS__COMCODE news_article

o AUTO_LINK news_category ( → news_categories.id)

o URLPATH news_image

o INTEGER news_views

o LONG_TEXT notes

o MEMBER submitter

o SHORT_TRANS__COMCODE title

o BINARY validated

news_categories

o AUTO id (Key field)

o ID_TEXT nc_img

o MEMBER nc_owner (May be NULL)

o SHORT_TRANS nc_title

o LONG_TEXT notes

news_category_entries

o AUTO_LINK news_entry ( → news.id) (Key field)

o AUTO_LINK news_entry_category ( → news_categories.id) (Key field)

news_rss_cloud

o AUTO id (Key field)

o TIME register_time

o IP rem_ip

o SHORT_TEXT rem_path

o INTEGER rem_port

Page 38: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o ID_TEXT rem_procedure

o ID_TEXT rem_protocol

o URLPATH watching_channel

newsletter newsletter_archive

o INTEGER date_and_time

o AUTO id (Key field)

o INTEGER importance_level

o ID_TEXT language

o LONG_TEXT newsletter

o SHORT_TEXT subject

newsletter_drip_send

o SHORT_TEXT d_from_email

o SHORT_TEXT d_from_name

o BINARY d_html_only

o TIME d_inject_time

o LONG_TRANS__COMCODE d_message

o SHORT_INTEGER d_priority

o SHORT_TEXT d_subject

o ID_TEXT d_template

o SHORT_TEXT d_to_email

o SHORT_TEXT d_to_name

o AUTO id (Key field)

newsletter_periodic

o AUTO id (Key field)

o LONG_TEXT np_csv_data

o SHORT_INTEGER np_day

o SHORT_TEXT np_frequency

o SHORT_TEXT np_from_email

o SHORT_TEXT np_from_name

o BINARY np_html_only

o BINARY np_in_full

o LANGUAGE_NAME np_lang

o TIME np_last_sent

o LONG_TEXT np_message

o SHORT_INTEGER np_priority

o LONG_TEXT np_send_details

Page 39: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o LONG_TEXT np_subject

o ID_TEXT np_template

newsletter_subscribe

o SHORT_TEXT email (Key field)

o AUTO_LINK newsletter_id ( → newsletters.id) (Key field)

o SHORT_INTEGER the_level

newsletter_subscribers

o INTEGER code_confirm

o SHORT_TEXT email

o AUTO id (Key field)

o TIME join_time

o ID_TEXT language

o SHORT_TEXT n_forename

o SHORT_TEXT n_surname

o ID_TEXT pass_salt

o SHORT_TEXT the_password

newsletters

o LONG_TRANS description

o AUTO id (Key field)

o SHORT_TRANS title

points chargelog

o INTEGER amount

o TIME date_and_time

o AUTO id (Key field)

o MEMBER member_id

o SHORT_TRANS__COMCODE reason

gifts

o INTEGER amount

o BINARY anonymous

o TIME date_and_time

o MEMBER gift_from

o MEMBER gift_to

o AUTO id (Key field)

o SHORT_TRANS__COMCODE reason

leader_board

o TIME date_and_time (Key field)

o MEMBER lb_member (Key field)

Page 40: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o INTEGER lb_points

pointstore prices

o ID_TEXT name (Key field)

o INTEGER price

pstore_customs

o INTEGER c_cost

o LONG_TRANS__COMCODE c_description

o BINARY c_enabled

o LONG_TRANS c_mail_body

o SHORT_TRANS c_mail_subject

o BINARY c_one_per_member

o SHORT_TRANS c_title

o AUTO id (Key field)

pstore_permissions

o AUTO id (Key field)

o ID_TEXT p_category ( → *)

o INTEGER p_cost

o LONG_TRANS__COMCODE p_description

o BINARY p_enabled

o INTEGER p_hours (May be NULL)

o LONG_TRANS p_mail_body

o SHORT_TRANS p_mail_subject

o ID_TEXT p_module

o ID_TEXT p_page ( → modules.module_the_name)

o ID_TEXT p_privilege ( → privilege_list.the_name)

o SHORT_TRANS p_title

o ID_TEXT p_type

o ID_TEXT p_zone ( → zones.zone_name)

sales

o TIME date_and_time

o SHORT_TEXT details

o SHORT_TEXT details2

o AUTO id (Key field)

o MEMBER memberid

o ID_TEXT purchasetype

polls

Page 41: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

poll

o INTEGER add_time

o SHORT_INTEGER allow_comments

o BINARY allow_rating

o BINARY allow_trackbacks

o TIME date_and_time (May be NULL)

o TIME edit_date (May be NULL)

o AUTO id (Key field)

o BINARY is_current

o LONG_TEXT notes

o SHORT_INTEGER num_options

o SHORT_TRANS__COMCODE option1

o SHORT_TRANS__COMCODE option10 (May be NULL)

o SHORT_TRANS__COMCODE option2

o SHORT_TRANS__COMCODE option3 (May be NULL)

o SHORT_TRANS__COMCODE option4 (May be NULL)

o SHORT_TRANS__COMCODE option5 (May be NULL)

o SHORT_TRANS__COMCODE option6 (May be NULL)

o SHORT_TRANS__COMCODE option7 (May be NULL)

o SHORT_TRANS__COMCODE option8 (May be NULL)

o SHORT_TRANS__COMCODE option9 (May be NULL)

o INTEGER poll_views

o SHORT_TRANS__COMCODE question

o MEMBER submitter

o INTEGER votes1

o INTEGER votes10

o INTEGER votes2

o INTEGER votes3

o INTEGER votes4

o INTEGER votes5

o INTEGER votes6

o INTEGER votes7

o INTEGER votes8

o INTEGER votes9

poll_votes

o AUTO id (Key field)

o AUTO_LINK v_poll_id ( → poll.id)

o MEMBER v_voter_id (May be NULL)

Page 42: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o IP v_voter_ip

o SHORT_INTEGER v_vote_for (May be NULL)

quizzes quiz_entries

o AUTO id (Key field)

o MEMBER q_member

o AUTO_LINK q_quiz ( → quizzes.id)

o INTEGER q_results

o TIME q_time

quiz_entry_answer

o AUTO id (Key field)

o LONG_TEXT q_answer

o AUTO_LINK q_entry ( → quiz_entries.id)

o AUTO_LINK q_question ( → quiz_questions.id)

quiz_member_last_visit

o AUTO id (Key field)

o MEMBER v_member_id

o AUTO_LINK v_quiz_id ( → quizzes.id)

o TIME v_time

quiz_question_answers

o AUTO id (Key field)

o SHORT_TRANS__COMCODE q_answer_text

o LONG_TRANS q_explanation

o BINARY q_is_correct

o INTEGER q_order

o AUTO_LINK q_question ( → quiz_questions.id)

quiz_questions

o AUTO id (Key field)

o BINARY q_marked

o INTEGER q_order

o LONG_TRANS__COMCODE q_question_extra_text

o LONG_TRANS__COMCODE q_question_text

o AUTO_LINK q_quiz ( → quizzes.id)

o BINARY q_required

o ID_TEXT q_type

quiz_winner

o AUTO_LINK q_entry ( → quiz_entries.id) (Key field)

o AUTO_LINK q_quiz ( → quizzes.id) (Key field)

Page 43: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o INTEGER q_winner_level

quizzes

o AUTO id (Key field)

o TIME q_add_date

o TIME q_close_time (May be NULL)

o LONG_TRANS__COMCODE q_end_text

o LONG_TRANS__COMCODE q_end_text_fail

o SHORT_TRANS q_name

o LONG_TEXT q_notes

o INTEGER q_num_winners

o TIME q_open_time

o INTEGER q_percentage

o INTEGER q_points_for_passing

o INTEGER q_redo_time (May be NULL)

o BINARY q_reveal_answers

o BINARY q_shuffle_answers

o BINARY q_shuffle_questions

o LONG_TRANS__COMCODE q_start_text

o MEMBER q_submitter

o AUTO_LINK q_tied_newsletter ( → newsletters.id) (May be NULL)

o INTEGER q_timeout (May be NULL)

o ID_TEXT q_type

o BINARY q_validated

redirects_editor redirects

o ID_TEXT r_from_page (Key field)

o ID_TEXT r_from_zone ( → zones.zone_name) (Key field)

o BINARY r_is_transparent

o ID_TEXT r_to_page

o ID_TEXT r_to_zone ( → zones.zone_name)

search searches_logged

o AUTO id (Key field)

o LONG_TEXT s_auxillary

o MEMBER s_member_id

o INTEGER s_num_results

Page 44: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT s_primary

o TIME s_time

searches_saved

o AUTO id (Key field)

o LONG_TEXT s_auxillary

o MEMBER s_member_id

o SHORT_TEXT s_primary

o TIME s_time

o SHORT_TEXT s_title

securitylogging banned_ip – list of banned IP addresses (Composr will use .htaccess also if it can, to improve performance)

o IP ip (Key field)

o BINARY i_ban_positive

o TIME i_ban_until (May be NULL)

o LONG_TEXT i_descrip

hackattack

o LONG_TEXT data_post

o TIME date_and_time

o AUTO id (Key field)

o IP ip

o MEMBER member_id

o ID_TEXT reason

o SHORT_TEXT reason_param_a

o SHORT_TEXT reason_param_b

o SHORT_TEXT referer

o URLPATH url

o SHORT_TEXT user_agent

o SHORT_TEXT user_os

usersubmitban_member – list of banned members

o MEMBER the_member (Key field)

shopping shopping_cart

o AUTO id (Key field)

o BINARY is_deleted

o MEMBER ordered_by ( → f_members.id)

o REAL price

o REAL price_pre_tax

Page 45: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT product_code

o LONG_TEXT product_description

o AUTO_LINK product_id ( → catalogue_entries.id)

o SHORT_TEXT product_name

o SHORT_TEXT product_type

o REAL product_weight

o INTEGER quantity

o ID_TEXT session_id

shopping_logging

o TIME date_and_time

o MEMBER e_member_id (Key field)

o AUTO id (Key field)

o IP ip

o SHORT_TEXT last_action

o ID_TEXT session_id

shopping_order

o TIME add_date

o INTEGER c_member

o AUTO id (Key field)

o LONG_TEXT notes

o ID_TEXT order_status

o SHORT_TEXT purchase_through

o ID_TEXT session_id

o BINARY tax_opted_out

o REAL tot_price

o SHORT_TEXT transaction_id

shopping_order_addresses

o SHORT_TEXT address_city

o SHORT_TEXT address_country

o SHORT_TEXT address_name

o SHORT_TEXT address_state

o LONG_TEXT address_street

o SHORT_TEXT address_zip

o SHORT_TEXT contact_phone

o SHORT_TEXT first_name

o AUTO id (Key field)

o SHORT_TEXT last_name

o AUTO_LINK order_id ( → shopping_order.id) (May be NULL)

Page 46: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o SHORT_TEXT receiver_email

shopping_order_details

o SHORT_TEXT dispatch_status

o AUTO id (Key field)

o REAL included_tax

o AUTO_LINK order_id ( → shopping_order.id) (May be NULL)

o SHORT_TEXT p_code

o AUTO_LINK p_id ( → catalogue_entries.id) (May be NULL)

o SHORT_TEXT p_name

o REAL p_price

o INTEGER p_quantity

o SHORT_TEXT p_type

sms confirmed_mobiles

sms_log – logs what SMS messages were sent out on behalf of what users and when

o AUTO id (Key field)

o MEMBER s_member_id

o TIME s_time

o IP s_trigger_ip

stats ip_country

o UINTEGER begin_num

o SHORT_TEXT country

o UINTEGER end_num

o AUTO id (Key field)

stats

o INTEGER access_denied_counter

o SHORT_TEXT browser

o TIME date_and_time

o AUTO id (Key field)

o IP ip

o MEMBER member_id

o INTEGER milliseconds

o SHORT_TEXT operating_system

o LONG_TEXT post

o URLPATH referer

o ID_TEXT session_id

Page 47: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o URLPATH s_get

o SHORT_TEXT the_page

usersonline_track

o TIME date_and_time (Key field)

o INTEGER peak

tickets ticket_extra_access

o MEMBER member_id (Key field)

o SHORT_TEXT ticket_id (Key field)

ticket_known_emailers

o SHORT_TEXT email_address (Key field)

o MEMBER member_id

ticket_types

o TIME cache_lead_time (May be NULL)

o BINARY guest_emails_mandatory

o AUTO id (Key field)

o BINARY search_faq

o SHORT_TRANS ticket_type_name

tickets

o AUTO_LINK forum_id ( → f_forums.id)

o SHORT_TEXT ticket_id (Key field)

o AUTO_LINK ticket_type ( → ticket_types.id)

o AUTO_LINK topic_id ( → f_topics.id)

welcome_emails f_welcome_emails

o AUTO id (Key field)

o SHORT_TEXT w_name

o AUTO_LINK w_newsletter ( → newsletters.id) (May be NULL)

o INTEGER w_send_time

o SHORT_TRANS w_subject

o LONG_TRANS w_text

o AUTO_LINK w_usergroup ( → f_groups.id) (May be NULL)

o ID_TEXT w_usergroup_type

wiki wiki_children

o AUTO_LINK child_id ( → wiki_pages.id) (Key field)

Page 48: compo.sr  · Web viewThe data types used here are our standard Composr schema types, which map onto SQL types. You can see the exact types used by browsing through an actual Composr

o AUTO_LINK parent_id ( → wiki_pages.id) (Key field)

o INTEGER the_order

o SHORT_TEXT title

wiki_pages

o TIME add_date

o LONG_TRANS__COMCODE description

o TIME edit_date (May be NULL)

o BINARY hide_posts

o AUTO id (Key field)

o LONG_TEXT notes

o MEMBER submitter

o SHORT_TRANS title

o INTEGER wiki_views

wiki_posts

o TIME date_and_time

o TIME edit_date (May be NULL)

o AUTO id (Key field)

o MEMBER member_id

o AUTO_LINK page_id ( → wiki_pages.id)

o LONG_TRANS__COMCODE the_message

o BINARY validated

o INTEGER wiki_views

wordfilter wordfilter

o AUTO id (Key field)

o SHORT_TEXT word

o SHORT_TEXT w_replacement

o BINARY w_substr (Key field)