3.1.1

Patch version 3.1.1 delivers better error handling of potential error conditions, where the ScriptEngine could not initialize properly or the execution fails due to OutOfMemoryError

3.1.0

Version 3.1.0 brings a number of performance improvements around the handling of Node.js processes and other internals.

3.0.0

Version 3.0.0 brings a massive number of stability and usability improvements -- including the precise reporting of the user script on execution failures. The syntax of the custom command used to switch between ScriptEngines has changed slightly from set-ScriptEngine to setScriptEngine.

The feature highlight of this release is the ability that one can switch between JVM languages (ScriptEngines) within the same connection and reference variables declared in the same session (JDBC connection) in another language.

The benefit of this is that the power of two different languages can be combined. You can for instance fetch data in Groovy and process it in Clojure or write a Scala script to generate data and then analyse it in R language (using Renjin Script Engine) with the full power of the JVM ...

Sample
Imagine one connects to the Groovy ScriptEngine using jdbc:dyna4jdbc:scriptengine:Groovy

msg = 'Hello World' // Variable declared in Groovy
dyna4jdbc:setScriptEngine javascript // Custom dyna4jdbc command: Language is set to JavaScript
// Script seamlessly continues in another language, JavaScript
print(msg);  // JavaScrip print method is called with the variable declared in Groovy!

2.5.0

Version 2.5.0 adds a major feature to ScriptEngine connections: one can now switch between ScriptEngines within the same connection and reference variables declared in another language.

Sample
Imagine one connects to the Groovy ScriptEngine using jdbc:dyna4jdbc:scriptengine:Groovy

msg = 'Hello World'" // Variable declared in Groovy
dyna4jdbc:set-ScriptEngine javascript // Custom dyna4jdbc command: Language is set to JavaScript
// Script seamlessly continues in another language, JavaScript
print(msg);  // JavaScrip print method is called with the variable declared in Groovy!

In addition to that, experimental-process-executor has been renamed to process-runner to reflect the stability improvements. From this version on, process-runner connection type requires specifying either endOfDataRegex or externalCallQuietPeriodMeansFinishedThreshold_ms.

1.8.0

Version 1.8.0 adds support for using Node.js through the JDBC API.

Now you can write your reports in pure Node.js JavaScript, output the results with console.log() and visualize the data in your favorite JDBC-enabled reporting tool.

The JDBC connection URL is jdbc:dyna4jdbc:nodejs

NOTE: Node.js has to be present on your system before you can use it. The driver invokes node command on your computer!

1.0.0

The first publicly available final version of dyna4jdbc

1.0.0 RELEASE CANDIDATE 1

The first official "RELEASE CANDIDATE" version of dyna4jdbc comes with a number of internal enhancements.

The Java ScriptEngine-based connection component is now considered production-ready. The URL format is jdbc:dyna4jdbc:scriptengine:<Script engine name> for example: jdbc:dyna4jdbc:scriptengine:JavaScript

Until the feature is finalized, connections using the external process runner component have to use the jdbc:dyna4jdbc:experimental-process-runner URL format.

0.9.1

The second official "beta" version of dyna4jdbc to demonstrate features. This release brings a number of stability improvements and bug fixes.

New feature: initScript configuration parameter allows a script file to specified, which should be execute each time a connection is established.

You can use this feature to e.g. pre-define frequently used methods and variables (service URLs etc)

The following URL demonstrates specifying the following settings in the JDBC connection string:
1.) Connecting to Groovy ScriptEngine and
2.) supplying the Groovy runtime JAR file location (c:/DEV/groovy-all-2.4.6.jar)
3.) instructing the driver to invoke the groovy script from c:/DEV/groovy-init.groovy every time the JDBC connection is established

jdbc:dyna4jdbc:scriptengine:groovy:classpath=c:/DEV/groovy-all-2.4.6.jar;initScript=c:/DEV/groovy-init.groovy

NOTE: if the init script cannot be found or raises any error, the connection attempt will fail.

Release 0.9

Release 0.9

The first official "pre-release" version dyna4jdbc to demonstrate capabilities. The dyna4jdbc driver now can load additional external JAR files specified in the connection URL allowing it to be used inside OSGI containers like Eclipse BIRT.

The following URL demonstrates using Groovy ScriptEngine and supplying the JAR file location in the JDBC connection string:

jdbc:dyna4jdbc:scriptengine:groovy:classpath=c:/DEV/groovy-all-2.4.6.jar