Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
8 check-ins related to "json-meta-data"
|
2022-11-18
| ||
| 19:28 | Add the ability to specify a description for each ticket report format. The user and reportfmt tables are updated with a new jx column containing JSON that describes the new features. (The user.jx table is currently not used but it was convenient to add it at the same time.) check-in: fcf17b28a9 user: drh tags: trunk | |
| 19:23 | Make sure the reportfmt table contains the jx column before trying to use that column. Leaf check-in: d433272527 user: drh tags: json-meta-data | |
| 19:20 | Use the "name" query parameter to select a report number. The legacy "rn" query parameter still works, but generated hyperlinks now use the new format. check-in: 3048c04b2a user: drh tags: json-meta-data | |
| 18:50 | Provide the ability to add custom header text on all ticket reports. The header and its mimetype are stored in the REPORTFMT.JX column. check-in: c06a9980c3 user: drh tags: json-meta-data | |
| 18:33 | Give the JX column of USER and REPORTFMT a default value which is valid JSON. check-in: 2433964d8f user: drh tags: json-meta-data | |
| 12:11 | Factor out the ALTER TABLE statements that add the JX column to the USER and REPORTFMT tables into separate subroutines. check-in: 8f6d7dacbb user: drh tags: json-meta-data | |
|
2022-11-17
| ||
| 23:38 | Add the "jx" column to the "user" and "reportfmt" tables, with the intent of using the column for JSON metadata. Currently unused. Make arrangements to sync the "jx" column (using the "fossil config" command) in a way that is backwards compatible with older versions that do not have the "jx" column. check-in: b7ac178c4f user: drh tags: json-meta-data | |
| 07:45 | Increase the version number to 2.21 to start the next development cycle. check-in: 8dcee00837 user: danield tags: trunk | |