Skip to content

registry: add SQLcl (aqua:oracle.com/sqlcl)#10417

Merged
jdx merged 3 commits into
jdx:mainfrom
jasonlyle88:registry-sqlcl
Jun 14, 2026
Merged

registry: add SQLcl (aqua:oracle.com/sqlcl)#10417
jdx merged 3 commits into
jdx:mainfrom
jasonlyle88:registry-sqlcl

Conversation

@jasonlyle88

@jasonlyle88 jasonlyle88 commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Adds a registry entry for Oracle's SQLcl, the CLI tool for Oracle databases. This is backed by the aqua:oracle.com/sqlcl package.

https://www.oracle.com/database/sqldeveloper/technologies/sqlcl/

This is the official Oracle CLI tool for interfacing with the database. In addition to interfacing with the database, it has an integrated MCP server and embeds liquibase (which is already an available mise tool), among many other features for Oracle databases.

SQLcl is released on a quarterly schedule (at minimum), with the current release always available here and all previous supported releases always available here. The most recent releases have been on:

  • 05.14.2026
  • 04.02.2026
  • 01.23.2026
  • 12.17.2025
  • 10.06.2025

This is released directly by Oracle, so I don't have a star count or any direct metrics.

In lieu of this, I offer the popularity of the GUI counterpart: https://marketplace.visualstudio.com/items?itemName=Oracle.sql-developer. This had 887,521 installs at the time of writing this PR. Obviously not a direct correlation, but I think a pretty strong indicator of the popularity as it it truly is just a GUI around the tool (a connection created in one will show up in the other even).

One note in case you go digging: the github repo backing the aqua package is just a release metadata repository to allow for version discovery and checksum verification. So the fact that is is new (I recently created it for the purpose of aqua/mise!) and doesn't have stars is not surprising... its not really supposed to be a visible repo.

Summary by CodeRabbit

  • New Features
    • Added Oracle SQLcl tool support for command-line SQL operations, including built-in version verification and Java dependency handling.

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1aaf7fbe-1916-47b9-8110-6de1290eeb70

📥 Commits

Reviewing files that changed from the base of the PR and between 46373c7 and 1339811.

📒 Files selected for processing (1)
  • registry/sqlcl.toml
✅ Files skipped from review due to trivial changes (1)
  • registry/sqlcl.toml

📝 Walkthrough

Walkthrough

A new registry entry registry/sqlcl.toml is added for Oracle SQLcl, defining its description, aqua backend, and a version verification test (sql -V expecting SQLcl output with java as a required toolchain).

Changes

SQLcl Registry Entry

Layer / File(s) Summary
SQLcl registry definition
registry/sqlcl.toml
Adds a 3-line TOML file declaring the Oracle SQLcl tool with its description, aqua:oracle.com/sqlcl backend, and a test command (sql -V) that checks for SQLcl in output and requires java.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops in with a scroll so neat,
SQLcl joins the registry fleet! 🐇
With java in tow and sql -V to test,
Oracle's CLI now passes the rest.
Hop, hop, hooray — one TOML line at a time! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and specifically summarizes the main change: adding a registry entry for SQLcl with the aqua:oracle.com/sqlcl backend.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds a single-file registry entry for Oracle SQLcl (oracle.com/sqlcl via the aqua backend), enabling mise use sqlcl as a shorthand. The entry follows the established file format exactly — backend, description, and test with a java tool dependency — matching the pattern used by the existing liquibase registry entry.

  • registry/sqlcl.toml uses the preferred aqua: backend tier and is correctly structured with backends, description, and test fields.
  • The tools = ["java"] dependency declaration mirrors the pattern used by liquibase.toml for other Java-based CLI tools.

Confidence Score: 5/5

The change is a single minimal TOML registry entry; it cannot break existing functionality and is technically well-formed.

The file is a three-line registry stub with correct syntax and a format consistent with all other Java-backed registry entries. There are no logic paths to break and no code changes beyond the registry file itself.

No files require special attention.

Important Files Changed

Filename Overview
registry/sqlcl.toml New registry entry for Oracle SQLcl; format is correct, aqua backend is the preferred tier, Java dependency matches the liquibase pattern.

Reviews (2): Last reviewed commit: "Pass lint" | Re-trigger Greptile

Comment thread registry/sqlcl.toml Outdated
Comment on lines +1 to +3
description = "Oracle SQLcl command-line interface for Oracle Database"
backends = ["aqua:oracle.com/sqlcl"]
test = { cmd = "sql -V", expected = "SQLcl", tools = ["java"] }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Missing GitHub star count in PR description

The repository's contribution guidelines require that new registry tool PRs include a GitHub star popularity count. The PR description explicitly states there is no star count and substitutes VSCode extension install metrics instead. The backing GitHub repo (jasonlyle88/sqlcl) was created specifically for aqua/mise packaging, so it will have near-zero stars — but the rule exists to gate tool popularity, and the proxy metric provided (extension installs for a different product) doesn't satisfy the stated requirement.

Rule Used: What: new registry tools must include the github s... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@github-actions

Copy link
Copy Markdown

This PR currently has failing checks. If this continues for 7 days, it will be closed automatically.

This is warning day 1 of 7.

Please update the PR when you have a chance. Feel free to reopen or create a new PR if it is closed and you'd like to continue working on it.

This comment was generated by an automated workflow.

Comment thread registry/sqlcl.toml
@@ -0,0 +1,3 @@
backends = ["aqua:oracle.com/sqlcl"]
description = "Oracle SQLcl command-line interface for Oracle Database"
test = { cmd = "sql -V", expected = "SQLcl", tools = ["java"] }

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's a bold name for the cli

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something you can only get away with when you're Oracle

@jdx jdx merged commit e78a36a into jdx:main Jun 14, 2026
34 checks passed
@jasonlyle88 jasonlyle88 deleted the registry-sqlcl branch June 14, 2026 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants