What inspired this wish list request?
We want to store log and debug messages of our addin-ins in a local database which can be used later for debugging purposes and we have seen that JMP has an internal SQLite support meaning that there does not need an ODBC driver to be installed.
Currently in JMP 16, 17 and 18 EA2 the internal support for SQLite is only for read (=SELECT) operations and the internal SQLIte operation has an over 8 year old version 3.8.11.1. Neither of both limitations are documented in the JMP documentation or can be found somewhere else.
E.g. the following command opens a SQLite database file in JMP:
obj = New SQL Query(
Connection("SQLite:Database=<path>\data.db"),
Custom SQL("SELECT sqlite_version(), sqlite_source_id() FROM table1")
) << Run Foreground();
BTW this command returns the version of the internally used SQLite implementation of JMP 16/17/18EA2:
| sqlite_version | sqlite_source_id |
| 3.8.11.1 | 2015-07-29 20:00:57 cf538e2783e468bbc25e7cb2a9ee64d3e0e80b2f |
But the next INSERT- or UPDATE-command results in an error: "deleted object reference[]"
obj = New SQL Query(
Connection("SQLite:Database=<path>\data.db"),
Custom SQL("INSERT INTO table1 (id, name, data) VALUES (1, \!"test\!", sqlite_version());")
) << Run Foreground();
What is the improvement you would like to see?
- Allow the SQLite implementation to execute UPDATE- and INSERT-statements to store data gathered while executing a JMP add-in.
- Update the internal SQLite driver so that a more recent version of the driver can be used - current version is 3.42.0
Why is this idea important?
This idea allows storage small data for debugging or logging purposes into the SQLite database files - this format is better, more flexible and more usable than using plain text, JSON or XML files.
@martindemel