SQL Developer Archives - Philipp Salvisberg's Blog https://www.salvis.com/blog/tag/sql-developer/ Database-centric development Mon, 27 Jul 2026 09:17:27 +0000 en-US hourly 1 https://wordpress.org/?v=7.0.2 https://www.salvis.com/blog/wp-content/uploads/2014/04/favicon.png SQL Developer Archives - Philipp Salvisberg's Blog https://www.salvis.com/blog/tag/sql-developer/ 32 32 The Return of SQLcl’s SCRIPT Command https://www.salvis.com/blog/2026/07/25/the-return-of-sqlcls-script-command/ https://www.salvis.com/blog/2026/07/25/the-return-of-sqlcls-script-command/#comments Sat, 25 Jul 2026 14:02:15 +0000 https://www.salvis.com/blog/?p=21049 Introduction The script command was introduced with SQLcl 4.2. It is based on JSR 223, the Java Scripting API, and makes it possible to run JavaScript from SQLcl. This adds client-side control flow, file access, better control of host commands and access to Java classes and JavaScript libraries. JDK 8 was the […]

The post The Return of SQLcl’s SCRIPT Command appeared first on Philipp Salvisberg's Blog.

]]> Introduction

The script command was introduced with SQLcl 4.2. It is based on JSR 223, the Java Scripting API, and makes it possible to run JavaScript from SQLcl. This adds client-side control flow, file access, better control of host commands and access to Java classes and JavaScript libraries.

JDK 8 was the latest and greatest back in 2015 when Kris Rice promoted this feature on his blog. The script command worked out of the box because JDK 8 included the Nashorn JavaScript engine. Nashorn was deprecated in JDK 11 and removed in JDK 15, but continues as a standalone OpenJDK library for JDK 11 and newer. The current version 26.2 of SQLcl requires JDK 11 or newer, but does not include a JavaScript engine. Therefore, script no longer works with a modern standard JDK.

The documented solution is to use GraalVM and install its JavaScript engine using the command gu install js. However, gu has been removed from more recent GraalVM distributions. Applications requiring a JavaScript engine must therefore provide the necessary Maven dependencies themselves.

Furthermore, the SQL Developer extension for VS Code comes with its own JDK 25. We cannot simply replace it with an older GraalVM JDK since some components require a JDK 25 and are therefore incompatible with older JDK versions.

The script command does not work in SQLcl embedded in SQL Developer for VS Code.

Let’s change that.

Patching SQLcl in SQL Developer for VS Code

I experimented with various approaches. The result is sqlcl-js-patch.sh. The idea is to download the missing JavaScript engine and its dependencies from Maven Central and add them to an SQLcl installation. This shell script supports GraalJS and Nashorn on JDK 17 and newer.

For SQL Developer for VS Code, I prefer Nashorn. It is compatible with the behaviour we had with JDK 8 and JDK 11 and produces no warnings when SQLcl starts.

Close all SQLcl sessions in VS Code. Then run the following command in a macOS, Linux or Git Bash shell:

1) Patch SQLcl with Nashorn JavaScript engine
curl --fail --location --silent --show-error \
  https://raw.githubusercontent.com/PhilippSalvisberg/sqlcl-js-patch/refs/heads/main/sqlcl-js-patch.sh |
  sh -s -- add nashorn "sqlcl_home=$HOME/.vscode"
Downloading nashorn-core-15.7.jar
Downloading asm-7.3.1.jar
Downloading asm-commons-7.3.1.jar
Downloading asm-analysis-7.3.1.jar
Downloading asm-tree-7.3.1.jar
Downloading asm-util-7.3.1.jar
No matching libraries found in /Users/phs/.vscode/extensions/oracle.sql-developer-26.2.0-darwin-arm64/dbtools/sqlcl/lib.
Installed nashorn-core-15.7.jar
Installed asm-commons-7.3.1.jar
Installed asm-7.3.1.jar
Installed asm-analysis-7.3.1.jar
Installed asm-util-7.3.1.jar
Installed asm-tree-7.3.1.jar
No nashorn.args VM option found in macOS/Linux launcher; skipped Nashorn launcher patch.
Installed nashorn libraries in /Users/phs/.vscode/extensions/oracle.sql-developer-26.2.0-darwin-arm64/dbtools/sqlcl/lib.

The patch script locates the most recent Oracle SQL Developer extension in the $HOME/.vscode/extensions directory. It adds the necessary JAR files to the embedded SQLcl, whose directory structure differs from that of standalone SQLcl.

Now start a new SQLcl session in VS Code and run:

2) Test script command
script
print('Hello from Nashorn');
/
SQLcl: Release 26.2 Production on Sat Jul 25 13:19:46 2026

Copyright (c) 1982, 2026, Oracle.  All rights reserved.

Connected to:
Oracle AI Database 26ai Free Release 23.26.2.0.0 - Develop, Learn, and Run for Free
Version 23.26.2.0.0

Hello from Nashorn
SQL>

This does not work when the code is executed directly in a SQL Developer worksheet. It works when you select Run in SQLcl.

That’s it. The script command is back.

Please note that updating the SQL Developer extension installs a new embedded SQLcl. In that case, run the patch command again.

Does It Work With GraalJS?

Yes.

Just pass graaljs instead of nashorn:

3) Patch SQLcl with GraalJS JavaScript engine
curl --fail --location --silent --show-error \
  https://raw.githubusercontent.com/PhilippSalvisberg/sqlcl-js-patch/refs/heads/main/sqlcl-js-patch.sh |
  sh -s -- add graaljs "sqlcl_home=$HOME/.vscode"
Downloading collections-25.1.3.jar
Downloading icu4j-25.1.3.jar
Downloading jniutils-25.1.3.jar
Downloading js-language-25.1.3.jar
Downloading js-scriptengine-25.1.3.jar
Downloading nativeimage-25.1.3.jar
Downloading polyglot-25.1.3.jar
Downloading regex-25.1.3.jar
Downloading truffle-api-25.1.3.jar
Downloading truffle-compiler-25.1.3.jar
Downloading truffle-runtime-25.1.3.jar
Downloading word-25.1.3.jar
Downloading xz-25.1.3.jar
Deleted nashorn-core-15.7.jar
Deleted asm-commons-7.3.1.jar
Deleted asm-7.3.1.jar
Deleted asm-analysis-7.3.1.jar
Deleted asm-util-7.3.1.jar
Deleted asm-tree-7.3.1.jar
Deleted asm-commons-7.3.1.jar
Deleted asm-analysis-7.3.1.jar
Deleted asm-tree-7.3.1.jar
Deleted asm-util-7.3.1.jar
Installed collections-25.1.3.jar
Installed regex-25.1.3.jar
Installed truffle-compiler-25.1.3.jar
Installed polyglot-25.1.3.jar
Installed truffle-api-25.1.3.jar
Installed jniutils-25.1.3.jar
Installed truffle-runtime-25.1.3.jar
Installed js-language-25.1.3.jar
Installed xz-25.1.3.jar
Installed word-25.1.3.jar
Installed icu4j-25.1.3.jar
Installed js-scriptengine-25.1.3.jar
Installed nativeimage-25.1.3.jar
Installed graaljs libraries in /Users/phs/.vscode/extensions/oracle.sql-developer-26.2.0-darwin-arm64/dbtools/sqlcl/lib.

Let’s start a new SQLcl session in VS Code and run:

4) Test script command
script
print('Hello from GraalJS');
/
Show/hide output 
SQLcl: Release 26.2 Production on Sat Jul 25 12:20:22 2026

Copyright (c) 1982, 2026, Oracle.  All rights reserved.

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.oracle.truffle.polyglot.JDKSupport in module org.graalvm.truffle (file:/Users/phs/.vscode/extensions/oracle.sql-developer-26.2.0-darwin-arm64/dbtools/sqlcl/lib/truffle-api-25.1.3.jar)
WARNING: Use --enable-native-access=org.graalvm.truffle to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.oracle.truffle.api.strings.TStringUnsafe (file:/Users/phs/.vscode/extensions/oracle.sql-developer-26.2.0-darwin-arm64/dbtools/sqlcl/lib/truffle-api-25.1.3.jar)
WARNING: Please consider reporting this to the maintainers of class com.oracle.truffle.api.strings.TStringUnsafe
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
Connected to:
Oracle AI Database 26ai Free Release 23.26.2.0.0 - Develop, Learn, and Run for Free
Version 23.26.2.0.0

[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot engine uses a fallback runtime that does not support runtime compilation to native code.
Execution without runtime compilation will negatively impact the guest application performance.
The following cause was found: JVMCI is not enabled for this JVM. Enable JVMCI using -XX:+EnableJVMCI.
For more information see: https://www.graalvm.org/latest/reference-manual/embed-languages/#runtime-optimization-support.
To disable this warning use the '--engine.WarnInterpreterOnly=false' option or the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
Hello from GraalJS
SQL>

After several warnings, the expected result appears at the end.

I explained the GraalJS-related warnings in my GitHub repository. The following environment setting will suppress most of the warnings. Where you define this variable depends on your operating system and shell. In any case, the environment variable must be visible before you start VS Code.

5) Non-breaking JDK_JAVA_OPTIONS to suppress warnings
export JDK_JAVA_OPTIONS="-Dpolyglot.engine.WarnInterpreterOnly=false -Dpolyglot.js.nashorn-compat=true"

If you are only using JDK 24 or newer on your system, you can disable all warnings as follows. However, be aware that any JDK version below 24 will no longer work, because the Java runtime stops with an error when passing unknown JVM arguments.

6) Breaking JDK_JAVA_OPTIONS to suppress warnings
export JDK_JAVA_OPTIONS="--illegal-native-access=allow --sun-misc-unsafe-memory-access=allow -Dpolyglot.engine.WarnInterpreterOnly=false -Dpolyglot.js.nashorn-compat=true"

Can I Also Use This for Standalone SQLcl?

Yes.

Pass the SQLcl installation directory instead of the VS Code configuration directory:

7) Patch standalone SQLcl with Nashorn JavaScript engine (macOS/Linux only)
curl --fail --location --silent --show-error \
  https://raw.githubusercontent.com/PhilippSalvisberg/sqlcl-js-patch/refs/heads/main/sqlcl-js-patch.sh |
  sh -s -- add nashorn "sqlcl_home=/path/to/sqlcl"

This works very well on macOS and Linux. Besides installing the Nashorn libraries, the patch removes the following option from the bin/sql launcher:

-Dnashorn.args=--no-deprecation-warning

The standalone Nashorn engine does not support this option. It throws an exception while the engine is initialised, and SQLcl consequently reports JavaScript engine not found.

On Windows, bin/sql.exe is a binary executable. The patch script cannot modify it. It can add the Nashorn libraries when run from Git Bash, but it cannot apply the necessary launcher workaround. Therefore, Nashorn does not work with standalone SQLcl on Windows. GraalJS does not need this launcher change and is therefore the only option supported by the patch script on Windows:

8) Patch standalone SQLcl with GraalJS JavaScript engine
curl --fail --location --silent --show-error \
  https://raw.githubusercontent.com/PhilippSalvisberg/sqlcl-js-patch/refs/heads/main/sqlcl-js-patch.sh |
  sh -s -- add graaljs "sqlcl_home=/path/to/sqlcl"

This raises an interesting question. SQL Developer for VS Code also includes a Windows bin/sql.exe that the patch script cannot modify. So why does Nashorn work there?

But Why Does Nashorn Work in Embedded SQLcl?

I mentioned before that the embedded SQLcl version has a different folder structure (there is no lib/ext folder for third-party libraries). But that’s not the only difference.

The launcher is also different. Neither bin/sql nor bin/sql.exe includes the -Dnashorn.args=--no-deprecation-warning JVM option.

As a result, the Nashorn JavaScript engine works in the embedded SQLcl version of SQL Developer for VS Code.

Outlook

I hope this helps you bring the SQLcl script command back to life in your environments, especially in SQL Developer for VS Code, where using another Java runtime is not a practical option.

However, I also hope that we will not have to run sqlcl-js-patch.sh for every new SQLcl or SQL Developer extension version until the end of time. The patch consists mainly of adding libraries that are available from Maven Central. It would be great if the Oracle SQL Developer team included these libraries in a future update and made the script command work out of the box again.

Updated on 2026-07-27, mentioned OpenJDK Nashorn in paragraph 2.

The post The Return of SQLcl’s SCRIPT Command appeared first on Philipp Salvisberg's Blog.

]]> https://www.salvis.com/blog/2026/07/25/the-return-of-sqlcls-script-command/feed/ 2 Installing SQL Developer in IDEs Implementing the VS Code Extension API https://www.salvis.com/blog/2025/07/05/installing-sql-developer-in-ides-implementing-the-vs-code-extension-api/ Sat, 05 Jul 2025 13:56:19 +0000 https://www.salvis.com/blog/?p=13951 Introduction The Oracle SQL Developer team is working on bringing the essential functionality built over the last 20 years in the classic SQL Developer IDE—a JDeveloper extension running as a standalone application—to the modern VS Code IDE. The integration with the VS Code ecosystem greatly enhances the developer experience. Is it time […]

The post Installing SQL Developer in IDEs Implementing the VS Code Extension API appeared first on Philipp Salvisberg's Blog.

]]> Introduction

The Oracle SQL Developer team is working on bringing the essential functionality built over the last 20 years in the classic SQL Developer IDE—a JDeveloper extension running as a standalone application—to the modern VS Code IDE. The integration with the VS Code ecosystem greatly enhances the developer experience.

Is it time to switch? – Well, it depends on which part of SQL Developer you use and how often. I’d say it’s time to start using the SQL Developer extension for VS Code. Use the classic SQL Developer when needed. You will do it less and less over time.

The SQL Developer extension is available in the VS Code Marketplace. That simplifies the installation for VS Code users. Unfortunately, this marketplace is not available in forks of VS Code or, more precisely, in IDEs that implement the VS Code extension API, such as VSCodium, Cursor, Windsurf and Theia IDE. So, how do we install VS Code extensions, specifically SQL Developer, in these IDEs? – I’ll answer this question in this blog post.

Installing SQL Developer in VS Code

The easiest way to install SQL Developer in VS Code is to start VS Code, search for oracle sql developer in the Extensions view, and click on the Install button. That’s it.

Install SQL Developer within VS Code

Please note that the second entry shown in the screenshot above is a deprecated/decommissioned extension developed by another team at Oracle. It’s a completely unrelated product.

Downloading SQL Developer’s .vsix File

At the time of writing, it is not possible (anymore) to download an extension such as SQL Developer directly from the VS Code Marketplace website. At least not officially. However, it’s possible in VS Code.

Instead of clicking on the install button as before, right-click on the extension and select Download VSIX.

Download VSIX file within VS Code

and then select the platform architecture.

Select the platform for which you want to download the VSIX

This is necessary because SQL Developer comes with a Java Runtime Environment, which contains platform-specific binaries.

Installing a VSIX File

VS Code, VSCodium, Cursor, Windsurf, and Theila IDE provide a Install from VSIX... command. You find it via View -> Command Pallette.... Run it,

Install from VSIX...

and select the VSIX file to install, and you’re done.

Open VSX Registry

Why are VSCodium, Cursor, Windsurf and Theia IDE not using the VS Code Marketplace? – Because the Terms of Use do not allow this. Here’s the relevant passage:

(…) you may not access, search, obtain or attempt to obtain any Offerings, materials, or information from the Sites through any means other than directly from Microsoft’s publicly supported interfaces (…)

This is why VSCodium, Cursor, Windsurf and Theia IDE use the alternative marketplace Open VSX Registry.

At the time of writing, the Oracle SQL Developer Extension for VSCode is not available in the Open VSX Registry. Here’s a screenshot of a search in Cursor:

Search for Oracle SQL Developer within Cursor

As you see, the deprecated/decommissioned extension is listed, but the successor is missing.

Summary

Installing an extension in VS Code via the integrated marketplace is super easy. Getting the .vsix file is also straightforward and enables the installation of VS Code extensions in IDEs that implement the VS Code extension API.

It would be great if the Oracle SQL Developer team published their SQL Developer extension on the Open VSX Registry too. This would make the initial installation and subsequent updates much simpler.

The post Installing SQL Developer in IDEs Implementing the VS Code Extension API appeared first on Philipp Salvisberg's Blog.

]]> Sharing SQL Developer Connections #JoelKallmanDay https://www.salvis.com/blog/2023/10/11/sharing-sql-developer-connections-joelkallmanday/ Tue, 10 Oct 2023 22:10:56 +0000 https://www.salvis.com/blog/?p=12481 1. The Problem I created a Docker image and a container for the Oracle Database 19c (19.19) for Linux ARM. The container contains ORDS, APEX and various sample schemas. Finally, an Oracle database that runs pretty fast on my Apple Silicon machine. Then I built a cold database clone by creating a […]

The post Sharing SQL Developer Connections #JoelKallmanDay appeared first on Philipp Salvisberg's Blog.

]]> 1. The Problem

I created a Docker image and a container for the Oracle Database 19c (19.19) for Linux ARM. The container contains ORDS, APEX and various sample schemas. Finally, an Oracle database that runs pretty fast on my Apple Silicon machine. Then I built a cold database clone by creating a container on another machine using a copy of the original Docker volume. So far, so good.

In SQL Developer I created a folder named odb190-localhost with 29 connections. Now I’d like to copy these SQL Developer connections to another machine. Easy, right? Export all connections to a JSON file and import it in the other SQL Developer instance. Yes, this works. But if you have several hundred connections like me, you get more than you want. The target installation might contain connection names with different properties. Therefore you do not want to import and overwrite existing connections and to identify and delete unwanted newly created connections after the import.

So, what can we do?

2. Some Possible Solutions

2.1. Export Only Wanted Connections

Exporting some chosen connections works technically. However, the export wizard does not support the concept of folders and presents a flat list of all connections. Selecting all connections in a folder is not feasible without sorting or filtering options in the UI.

SQL Developer export wizard

Finding all entries ending on odb190-localhost is no fun. It might work for a handful of connections, but not for 29.

2.2. Export Only One Template Connection

As an alternative, you can export just one connection and import it into the target SQL Developer installation. Use this connection as a kind of template. Click on the connection and select Properties in the context menu.

New / Select Database Connection in SQL Developer

In this window, you can change the Name, Username and Password and press Save. Repeat that process for all other connections. Either now or later when you need them.

Not really a satisfying solution either, right?

2.3. Export All Connections and Filter with VS Code

Exporting all connections is easy. Let’s look at the file in Visual Studio Code.

all-connections.json in VS Code (original)

This is a minified JSON. Let’s select Format Document from the context menu to make it human-readable.

all-connections.json in VS Code (formatted)

Ahh, much better.

Removing Unwanted info Objects

On line 11 we see the property NAV_FOLDER. We are only interested in connections with the value odb190-localhost. Is there a way to delete all unwanted entries? Yes, there is. By using jq, a command line utility to process JSON files. There is also an extension for VS Code named jq-vscode, which simplifies the development of a jq command.

Here’s the jq command to remove all unwanted info objects from the connections array:

jq command to remove unwanted connections
del(
    .connections[] 
    | select(.info.NAV_FOLDER!="odb190-localhost")
)

In VS Code you can open a split window via the command JQ: Open a new file to exec jq. There you can enter the jq command.

all-connections.json filtered with jq-vscode

In the lower part of the screen, you can see the result of the jq command. Copy the output and save it to a file to be imported into any SQL Developer installation.

2.4. Export All Connections and Filter with JQ CLI

This is basically the same solution as before. The only difference is that we use the jq command-line tool. jq is available on all major platforms (Linux, Windows, macOS). Download it from here or install it directly with your OS package installer (e.g. apt, yum, dnf, brew, …).

I exported all connections to a file named all-connections.json from SQL Developer.

With the following command, I produce the file odb190-localhost-connections.json that contains only the connections in the folder odb190-localhost:

jq CLI command to remove unwanted connections
jq 'del(.connections[] | select(.info.NAV_FOLDER!="odb190-localhost"))' \
    all-connections.json > odb190-localhost-connections.json

The file odb190-localhost-connections.json is ready to be shared and imported into other SQL Developer installations.

3. Conclusion

There are other solutions, not covered in this blog post, to create a filtered connection export from SQL Developer. For example, writing a dedicated SQL Developer extension. Or filtering an export file with another tool. Or processing a JSON export file in the database.

However, IMO jq is an excellent tool to process JSON data in shell scripts. Perfect for automation. In this case, it makes sharing a subset of your SQL Developer connections easier. For any filter criteria, you want to apply.

The post Sharing SQL Developer Connections #JoelKallmanDay appeared first on Philipp Salvisberg's Blog.

]]>