v2.4.0-rc1

• Removed MySQL support

Full Changelog: v2.3.4...v2.4.0-rc1

v2.3.4

• Deprecated MySQL support in documentation, will depreciate MySQL support in future release
• Improved loading large JSON objects from jsonl files
• Fixed issue #164 where the queries in COLD would work in v2.2.0 but fail in v2.3.x.
• Removed support for SQL parameters in dsquery due to encoding issues and lack of practical use cases
• Removed duplicated code from dsquery.go and api_routes.go in favor of collection.go's implementation of query functionality.
• Added tailing semi-colon removal for SQL queries due to changes in behavior of SQLite3 driver

Full Changelog: v2.3.3...v2.3.4

v2.3.3

• Issue #161 fix for handling GET with query were data is passed via URL parameters.
• Removed support for frame, clone, sample, sync and join support removed. The dsimporter cli removed (use jsonl dump and load instead).
• Improved loading large JSON objects from jsonl files

What's Changed

• Bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 by @dependabot[bot] in #162

Full Changelog: v2.3.2...v2.3.3

v2.3.2

Issue #161 fix for handling GET with query were data is passed via URL parameters.

Removed support for frame, clone, sample, sync and join support removed. The dsimporter cli removed (use jsonl dump and load instead).

Full Changelog: v2.3.1...v2.3.2

v2.3.1

Issue #152 has started. The frames, sample and clone help has been removed as those features are depreciated. The frames supprt was remove from datasetd. Help is being reorganizaed. api_doc.go and api_cmd.go was removed as it was dead code with changes in help implementaiton.

The -help option can pull up help on a topic by providing a keyword as a separate parameter. This let's you pull up help on the related commands.

Example:

dataset -help api
dastaet -help dsquery

Help text is now maintain inside a single file, helptext.go.

This while the code for frames, clone and sample remains in the dataset cli it'll be removed in an upcoming release before the transition to v2.4.

Full Changelog: v2.3.0...v2.3.1

v2.3.0

The object versioning problem identified in issue #149 persisted after the release of v2.2.8. The resulted in mitigation steps of ignoring the version.json file held in the collection's root directory. As of v2.3 this file is no longer read or updated. Instead the collection level methods will explicitly set the versioning type at the store level. This means one locations holds versioning state, the collection.json. This simplified the codebase and appears to be backward compatible. A simpler approach to versioning for JSON documents and attachments is planned for v3.

Full Changelog: v2.2.8...v2.3.0

v2.2.8

This release has focused on cleanup, bug fixes and documentation revisions.

• Fixes and mitigations for issues #148 and #149
• Implemented feature request issue #150

What's Changed

• V2.2.7 release by @rsdoiel in #147

Full Changelog: v2.2.7...v2.2.8

v2.2.7

This release has focused on cleanup, bug fixes and adding a redirect feature to support development without requiring JavaScript browser side.

• Fixed issue #138, where SQLite3 updated times where not set.
• Fixed issue #144, Fix issue with spurious form validation without a defined data model.
• Fixed issue #145, added support for create_success, and create_error which hold redirects for success and failure on POST that are URLencoded.
• Fixed issue #146, path handling to collection name caused me to mis-caculate the table name.

What's Changed

• V2 merge by @rsdoiel in #143

Full Changelog: v2.2.5...v2.2.7

v2.2.6

Fix runtime error, issue 142. Added cors setting when serving JavaScript files.

Full Changelog: v2.2.4...v2.2.6

v2.2.5

Added the following functions to the dataset package

• (c *Collection) KeysJSON
• (c *Collection) UpdatedKeysJSON
• (c *Collection) QueryJSON

These provide JSON encoded object support for their base functions.

In datasetd, requesting an API object without specifying the content type returns an application/json object.

Full Changelog: v2.2.4...v2.2.5