[eugenena]

Added SchemaSynchronizer project description to README.

Suggestion type

• Project
• Resource

Checklist

• I searched the list and existing issues for duplicates.
• I changed README_SOURCE.md, not the generated README.md.
• This pull request contains one suggestion.
• The suggestion is relevant to Java or the JVM and fits its chosen category.
• I used the canonical project or resource link.
• The suggestion is current and maintained.
• The concise, neutral description explains its distinguishing value and ends with punctuation.
• Licensing is clear and any restrictive terms are disclosed where applicable.

---

Summary by cubic

Adds SchemaSynchronizer to the database tools list in the README so developers can discover a tool that keeps relational schemas in sync with version-controlled definitions. The entry includes its Apache-2.0 license and a description clarifying that safe changes are applied automatically while destructive ones are surfaced as SQL for manual review.

^{Written for commit 85a6970. Summary will update on new commits.}

[cubic-dev-ai]

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. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:684">
P2: This edits the generated `README.md` directly, so the SchemaSynchronizer entry will disappear the next time the README is regenerated. Add the project to `README_SOURCE.md` under Database instead; the generator will supply its metadata and keep counts synchronized.</violation>
</file>

<sub>Reply to a comment to ask cubic a question or push back. It learns from your replies.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This edits the generated README.md directly, so the SchemaSynchronizer entry will disappear the next time the README is regenerated. Add the project to README_SOURCE.md under Database instead; the generator will supply its metadata and keep counts synchronized.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At README.md, line 684:

<comment>This edits the generated `README.md` directly, so the SchemaSynchronizer entry will disappear the next time the README is regenerated. Add the project to `README_SOURCE.md` under Database instead; the generator will supply its metadata and keep counts synchronized.</comment>

<file context>
@@ -681,6 +681,8 @@ _Everything that simplifies interactions with the database._
 
 > **[SchemaCrawler](https://github.com/schemacrawler/SchemaCrawler)** <kbd>★ 1.8k</kbd> 🟢<br>Discovers, documents and diagrams relational database schemas from Java, build tools and the command line.
 
+>**[SchemaSynchronizer](https://github.com/eugenena/SchemaSynchronizer)** <kbd>Apache-2.0</kbd>🟢<br>SchemaSynchronizer keeps a relational database aligned with a version-controlled schema definition. It applies additive and otherwise safe changes automatically, while returning destructive or ambiguous changes as SQL for a human operator to review.
+
 > **[Spring Data Dynamic Query](https://github.com/tdilber/spring-data-dynamic-query)** <kbd>★ 39</kbd> <kbd>Apache-2.0</kbd> 🟠<br>Unified dynamic query interface for Spring Data JPA, MongoDB, and Elasticsearch, enabling advanced JOIN(s), OR logic, scoped conditions, powerful projections and advanced features with zero boilerplate.
</file context>