Difference between revisions of "WikiDB/Roadmap"
From TestWiki
< WikiDB
(→Back-end: PostgreSQL support now added.) |
(OR is now implemented in my dev branch... still testing, but will be in next release!) |
||
| Line 13: | Line 13: | ||
* Data definitions in a DB namespace shouldn't require the 'table' attribute (default to current). | * Data definitions in a DB namespace shouldn't require the 'table' attribute (default to current). | ||
* Repeat tag syntax - some things to iron out (see [[WikiDB/Repeat tag syntax]] for the discussion) | * Repeat tag syntax - some things to iron out (see [[WikiDB/Repeat tag syntax]] for the discussion) | ||
| − | |||
* Repeat tag - Allow LIMIT argument (or maybe 'range'). | * Repeat tag - Allow LIMIT argument (or maybe 'range'). | ||
* Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table). Suggestion is to prefix the name with an exclamation mark. Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone... | * Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table). Suggestion is to prefix the name with an exclamation mark. Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone... | ||
| Line 25: | Line 24: | ||
== i18n / L10n == | == i18n / L10n == | ||
* Ensure all user-visible strings come from the message cache. | * Ensure all user-visible strings come from the message cache. | ||
| − | * The 'number' data type is not currently locale aware. | + | * The 'number' data type is not currently locale aware on input (renders correctly). |
Revision as of 23:35, 27 May 2015
This is an (incomplete) list of features that I plan to add. There are also good ideas from other people scattered around the wiki, which I should really add to this page, but haven't yet.
Note that this page reflects my current development version - if an item is removed from this page due to being implemented, it may not turn up in a public release for a little while.
The bug list has been moved to WikiDB/Bugs. Please report bugs there.
Back-end
- Add 'date' data-type.
- Joins in queries
- Foreign key definitions
Syntax
- Data definitions in a DB namespace shouldn't require the 'table' attribute (default to current).
- Repeat tag syntax - some things to iron out (see WikiDB/Repeat tag syntax for the discussion)
- Repeat tag - Allow LIMIT argument (or maybe 'range').
- Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table). Suggestion is to prefix the name with an exclamation mark. Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone...
Code Tidying
- Add profiling statements.
Administration
- 'What links here' should show templates that are included via data tags.
i18n / L10n
- Ensure all user-visible strings come from the message cache.
- The 'number' data type is not currently locale aware on input (renders correctly).
