Jump to content

MediaWiki/extensions: Difference between revisions

making some sense to this task of reviewing all existing extensions and switching from a line-separated list to a 6-column table starting from letter 'H'
(adding additional column for misc. notes)
(making some sense to this task of reviewing all existing extensions and switching from a line-separated list to a 6-column table starting from letter 'H')
Line 239: Line 239:


=== HashTables ===
=== HashTables ===
[[mw:Extension:HashTables]] - Enhances the parser with hash table functions and a function to store all parameters given to a template.


'''Us on HashTables:'''
{| class="wikitable"
BINGO! Now we need only a way to store these in a database and fetch them from the database and we're set for a system that we can edit wiki and get stored in database and edit database and wiki get affected.
|-
! Extension
! General description
! Consumium specific
! Implementation
! Compabilities
! Other notes
|-
| <tt>'''[[mw:Extension:HashTables]]'''</tt>
| Ability to make [[w:hash table]]s from template-data and to fill templates with data from hash tables. Enhances the parser with hash table functions and a function to store all parameters given to a template.
 
| This combined with storing and fetching to/from database so that database maybe manipulated from wiki and the wiki manipulated from the database. In some tasks [[#Arrays]] will be much more efficient, but as a catch-all way of storing values in templates in articles hash tables are an excellent idea.
| [[mw:Parser function]]
| Tested on 1.17
| BINGO! Now we need only a way to store these in a database and fetch them from the database and we're set for a system that we can edit wiki and get stored in database and edit database and wiki get affected. Naturally using [[#Arrays]] can be much more efficient then a hash table when there is much sequential access of values / keys tables .. Using a hash table to store all things and no arrays certainly makes much more sense then using an array to store all things and no hash tables.
|-
|
|
|
|
|
|
|}


Naturally using [[#Arrays]] can be much more efficient then a hash table when there is much sequential access of values / keys tables .. Using a hash table to store all things and no arrays certainly makes much more sense then using an array to store all things and no hash tables.


== N ==
== N ==
9,854

edits

We use only those cookies necessary for the functioning of the website.