Skip to content

add jquick-sql to Database section - #1298

Open
paohaijiao wants to merge 6 commits into
akullpp:mainfrom
paohaijiao:master
Open

add jquick-sql to Database section#1298
paohaijiao wants to merge 6 commits into
akullpp:mainfrom
paohaijiao:master

Conversation

@paohaijiao

@paohaijiao paohaijiao commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Why this belongs in awesome-java

This project fills a distinct gap in the Java ecosystem:

  • Unique value: Unlike traditional ORM tools or single-database connectors, jquick-sql provides a lightweight, embeddable federated query engine that can query across heterogeneous data sources (RDBMS, files, REST APIs) using standard SQL.
  • Innovative approach: Implements a Coordinator-Worker architecture with optimizations including predicate pushdown, join reorder, and two-phase aggregation, making distributed query execution accessible with minimal overhead.
  • Active maintenance: Project is actively maintained with regular updates and clear documentation.

Additional context

  • License: Apache 2.0
  • Project is open-source with clear contribution guidelines
  • Demonstrates comprehensive SQL feature support including JOINs, subqueries, aggregations, and set operations (UNION/INTERSECT/MINUS)

paohaijiao and others added 5 commits July 26, 2026 08:33

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:504">
P1: This project addition is made to the wrong file. README.md is generated from README_SOURCE.md (see the header comment and the GenerateReadme.java pipeline), and the repository's CI explicitly rejects direct README.md edits: the 'Reject direct README changes' step in .github/workflows/update-readme.yml fails the build with 'README.md is generated. Edit README_SOURCE.md instead.' when README.md is touched. Because the entry exists only in README.md and not in README_SOURCE.md, it also disappears the next time the README is regenerated, so the listing never actually ships. Move the JQuick SQL entry into the Database section of README_SOURCE.md (alongside the other DB entries, e.g. after Flyway) in the required `- [Name](URL) - description` format, and leave README.md untouched.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread README.md Outdated

> **[Flyway](https://github.com/flyway/flyway)** <kbd>★ 10.0k</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Simple database migration tool.

> **[JQuick SQL](https://github.com/paohaijiao/jquick-sql)** <kbd>★ 288</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Embeddable, lightweight distributed SQL engine featuring heterogeneous federated query support for unified data access across disparate systems.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1: This project addition is made to the wrong file. README.md is generated from README_SOURCE.md (see the header comment and the GenerateReadme.java pipeline), and the repository's CI explicitly rejects direct README.md edits: the 'Reject direct README changes' step in .github/workflows/update-readme.yml fails the build with 'README.md is generated. Edit README_SOURCE.md instead.' when README.md is touched. Because the entry exists only in README.md and not in README_SOURCE.md, it also disappears the next time the README is regenerated, so the listing never actually ships. Move the JQuick SQL entry into the Database section of README_SOURCE.md (alongside the other DB entries, e.g. after Flyway) in the required - [Name](URL) - description format, and leave README.md untouched.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 504:

<comment>This project addition is made to the wrong file. README.md is generated from README_SOURCE.md (see the header comment and the GenerateReadme.java pipeline), and the repository's CI explicitly rejects direct README.md edits: the 'Reject direct README changes' step in .github/workflows/update-readme.yml fails the build with 'README.md is generated. Edit README_SOURCE.md instead.' when README.md is touched. Because the entry exists only in README.md and not in README_SOURCE.md, it also disappears the next time the README is regenerated, so the listing never actually ships. Move the JQuick SQL entry into the Database section of README_SOURCE.md (alongside the other DB entries, e.g. after Flyway) in the required `- [Name](URL) - description` format, and leave README.md untouched.</comment>

<file context>
@@ -501,6 +501,8 @@ _Everything that simplifies interactions with the database._
 
 > **[Flyway](https://github.com/flyway/flyway)** <kbd>★ 10.0k</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Simple database migration tool.
 
+> **[JQuick SQL](https://github.com/paohaijiao/jquick-sql)** <kbd>★ 288</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Embeddable, lightweight distributed SQL engine featuring heterogeneous federated query support for unified data access across disparate systems.
+
 > **[H2](https://github.com/h2database/h2database)** <kbd>★ 4.6k</kbd> 🟢<br>Small SQL database notable for its in-memory functionality.
</file context>

Comment thread README.md Outdated
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