The amount of control fields (that are always present in modules) keeps growing which limits the field names available. Introducing the underscore in the _stp field was an attempt to make them unique enough to not collide with "normal" field names people may want.
The problem there however is that it currently can't be used in the templates format class as that uses underscores to indicate marker types (e.g. _if). This can of course be changed but that would mean all templates requir...
Currently JAS uses the Data field values to build up the WHERE clause in the SQL query (and Storage::_filterDataset) in a straightforward but limited way. It should be possible to get data via a more flexible method that allows for advanced nesting.
Example:
SELECT *
FROM blog_entries
LEFT JOIN blog_tagsmapping ON
blog_entries.nr=
blog_tagsmapping.blog_entries --automagically determined based on where clause
LEFT JOIN blog_tag...
JAS should support PostgreSQL (and optionally other databases). The post sensible way seems to be to have a base SQL class which contains the majority of the query components (SELECT, INSERT, UPDATE, DELETE, FROM, WHERE, ORDER BY, etc) which can be overridden by the extending classes.
An interesting option would be to use PDO for the base class as this will support more than just MySQL and PostgreSQL. Additionally it allows for "named variables" for prepared statements which should m...
Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.