Extension:DataTable2/Configuration

Rights
The extension defines a new right datatable2-specialpages needed to use the special pages, which is assigned by default to all registered users. You might decide to restrict this if you have so many DataTable2 data that use of the special pages degrades performance.

It is pointless to restrict this for security reasons since all DataTable2 data can be extracted using the &lt;dt2-showtable&gt; tag anyway. The extension does not intend to impose any restriction on use of these data.

LocalSettings.php
There is a number of parameters that can be customized in LocalSettings.php. They all have defaults which are likely to fit for many cases, so you can skip this section when installing the extension for the first time.


 * $wgDataTable2WriteDest
 * Name of the database table where data is written to.


 * $wgDataTable2ReadSrc
 * Name of the database table where data is read from.
 * You might set this to a view which is a union of $wgDataTable2Write and data from other sources which can then be read but not modified through this extension. In such a case, the data from other sources should leave the dtd_page column empty (NULL).


 * $wgDataTable2MetaWriteDest
 * Name of the database table where meta data is written to.


 * $wgDataTable2MetaReadSrc
 * Name of the table where meta data is read from.
 * You might set this to a view which is a union of $wgDataTable2MetaWriteDest and data from other sources which can then be read but not modified through this extension.


 * $wgDataTable2Args
 * Default arguments for &lt;datatable2&gt; tags.


 * $wgDataTable2SqlWhiteList
 * Array of identifiers that may be used in WHERE and ORDER BY clauses, in addition to column names.
 * Unquoted identifiers in where and order-by arguments are converted to uppercase, hence the items in $wgDataTable2SqlWhiteList should be uppercase unless they are deliberately case-sensitive. The default contains only some rather portable SQL functions, which are a small subset of those available in your database backend. Hence you are most likely to add functions to this. Since the extension uses a parser which considers the dot as part of an identifier, you may add qualified names like functions in packages or other schemas.


 * $wgDataTable2EnableDetailTracking
 * Tells whether a tracking category should be added for each single table.
 * The category names are created with the message datatable2-consumer-detail-category (in your wiki's content language).


 * $wgSpecialDataTable2PageParSep
 * Separator for parameters passed to special pages.
 * Parameters can be passed to special pages as subpage components. When more than one parameter is possible and a parameter could be a page name with a subpage, the slash cannot be used to separate the parameters. There is no obvious choice for the best separator since the characters which by default are not allowed in page titles cannot be used in internal links, either.


 * $wgSpecialDataTable2DataClasses
 * List of CSS classes for the table used in "Special:DataTable2Data".

Messages
Since the extension defines a lot of messages which are constantly evolving with further development, they are not documented here. Please refer to the $messages['qqq'] entry in the file DataTable2.i18n.php.

Database
By default, the extension allows up to 30 columns in a table. In the unlikely case that you would like to enlarge the maximum number of columns, you need to add columns to the table datatable2_data defined in the file datatable2_data.sql and to adapt the class constant DataTable2Database::MAX_FIELDS</tt> in the file DataTable2Database.php</tt>.

By default, the first 10 columns are indexed. In order to index more (or less) columns, you need to create (or drop) indexes; see file datatable2_data.sql</tt>.