Manual:Suitability of tables for sharing/de
Some tables lend themselves better than others to being shared using $wgSharedTables.
| Tabelle | Can be shared? | Anmerkungen |
|---|---|---|
| archive | Nein | ar_rev_id-Kollisionen |
| category | Nein | cat_title collisions |
| categorylinks | Nein | cl_from-Kollisionen |
| change_tag | Nein | ct_log_id collisions |
| comment | Nein | Houses comments linked to multiple unshareable tables. |
| externallinks | Nein | el_from-Kollisionen |
| filearchive | Nein | ? |
| image | Nein | To have a shared media repository, see $wgForeignFileRepos |
| imagelinks | Nein | il_from-Kollisionen |
| interwiki | Ja | The interwiki table contains mostly static data; it may be useful to share if you have many custom interwikis. |
| ipblocks | Ja | By sharing the ipblocks table, you can have "global blocks" so that a block on one wiki will block the user or IP on all other wikis using the shared database. There can be some minor issues when sharing the ipblocks table. Viz., the ipb_reason field is set as the "reason" on Special:Block when blocking a user. When a blocked user sees the "You are blocked" message, this is parsed as wikitext, and links are parsed on Special:BlockList, you will need to make sure when blocking a user that the message makes sense on all wikis. Also, block logs will not be shared. (You must also share your user table for shared ipblocks to work.)
Note that the comment table cannot be shared, which may cause issues with some blocking-related code, per phab:T214011. |
| iwlinks | Nein | iwl_from-Kollisionen |
| job | Nein | job_title collisions |
| l10n_cache | ? | ? |
| langlinks | Nein | ll_from-Kollisionen |
| linktarget | ? | ? |
| logging | Nein | log_page collisions |
| log_search | Nein | ls_value-Kollisionen |
| module_deps | ? | ? |
| objectcache | Ja | ? |
| oldimage | ? | ? |
| page | Nein | page_namespace and page_title collisions |
| pagelinks | Nein | pl_from-Kollisionen |
| page_props | Nein | pp_page collisions |
| page_restrictions | Nein | pr_page-Kollisionen |
| protected_titles | Nein | pt_namespace and pt_title collisions |
| querycache | Nein | qc_namespace and qc_title collisions |
| querycachetwo | Nein | qcc_namespace and qcc_title collisions |
| querycache_info | Nein | qc_type-Kollisionen |
| recentchanges | Nein | rc_cur_id collisions |
| redirect | Nein | rd_from-Kollisionen |
| revision | Nein | rev_page collisions |
| searchindex | Nein | si_page-Kollisionen |
| site_stats | Ja | The site_stats table could possibly be shared, to aggregate data over all your wikis. |
| tag_summary | Nein | ts_rc_id, ts_log_id, and ts_rev_id collisions |
| templatelinks | Nein | tl_from, tl_namespace and tl_title collisions |
| transcache | ? | ? |
| updatelog | ? | ? |
| uploadstash | ? | ? |
| user | Ja | A shared user table can be used to have multiple wikis that have shared user registrations, so that users need only sign up to one wiki. Siehe Handbuch:Gemeinsame Datenbank. |
| user_former groups | Ja | You would need to share the user table as well, and presumably user_groups. |
| user_groups | Ja | Sharing the user_groups table will allow you to have global user groups. As with the block log, the user rights log is not shared. |
| user_newtalk | ? | ? |
| user_properties | Ja | By default, the user_properties table is included in the list of shared tables. |
| valid_tag | ? | ? |
| watchlist | Nein | wl_namespace and wl_title collisions |