Extension:Cargo/Known bugs and planned features

Known bugs

 * The buttons in the 'calendar' display format (like "today") currently still have their values hard-coded in English.
 * There is currently no way to query on fields that hold a list of coordinates.
 * If a table is recreated via the web interface and the "job run rate" (set via $wgJobRunRate) is too high, it can lead to some pages not getting their data stored.
 * Cargo experiences issues in both storing and displaying data when the VisualEditor extension is also in use on the wiki.
 * Although Cargo in theory supports the MySQL, PostgreSQL, MS SQL Server, Oracle and SQLite database systems, in practice only MySQL and PostgreSQL have been tested; it is likely that there are bugs in the handling of one or more of the other systems.

Planned features
Many of the planned features for Cargo involve more closely matching the functionality of Semantic MediaWiki. In some cases, this may involve creating additional extensions that are meant to work with Cargo. For a detailed listing, see Cargo and Semantic MediaWiki#Features checklist.

Other features that it would be useful to add to Cargo include:
 * Allow for defining "child tables" for templates, so that all templates that show up together on certain pages can be queried and displayed together more easily, especially in Special:Drilldown.
 * Better automatic display of data, including automatic maps, calendars/timelines and bar charts for tables that contain fields of type Coordinates, Date/Datetime and Integer/Float, respectively.