Add LibreDB Studio to the list of supported GUI tools

[kaya-abdullah]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Adds LibreDB Studio (https://libredb.org, https://github.com/libredb/libredb-studio) to the GUI table in the third-party tools list. It's an open-source, web-based SQL IDE that connects to TiDB over the MySQL protocol.

Verified against a local TiDB Self-Managed instance (pingcap/tidb:v8.5.0, --store=unistore): created a connection, ran a query, created a table and read the rows back.

The Full rating reflects a broader measurement than that single session: the TiDB section of docs/providers/mysql.md in the LibreDB Studio repo independently tests all 15 provider surfaces against TiDB (schema browsing, query editing, EXPLAIN, health/monitoring, storage stats, permissions, and more) and documents the caveats found: background statistics lag on freshly loaded tables, EXPLAIN FORMAT='json' being rejected, an empty slow-query panel, and a phantom InnoDB storage entry.

A dedicated connection tutorial (like the ones DataGrip, DBeaver, VS Code and Navicat have) is not included in this PR, so the Tutorial column is N/A for now, same as the Beekeeper Studio row above it.

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• Other reference link(s): https://github.com/libredb/libredb-studio

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

Summary by CodeRabbit

• Documentation
  • Added LibreDB Studio to the list of GUI tools supported by TiDB.
  • Recorded compatibility as fully supported for version 0.13.4.
  • Noted that no tutorial is currently available.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign qiancai for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• develop/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Hi @kaya-abdullah. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

Welcome @kaya-abdullah!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[pingcap-cla-assistant]

All committers have signed the CLA.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 410e28a8-1ca9-45d7-82f9-5319df4bd7ea

📥 Commits

Reviewing files that changed from the base of the PR and between 0d5953c and c0f2729.

📒 Files selected for processing (1)

• develop/dev-guide-third-party-support.md

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The GUI support table now lists LibreDB Studio, tested with version 0.13.4. The entry marks support as Full and indicates that no tutorial is available.

Changes

GUI support documentation

Layer / File(s)	Summary
Add LibreDB Studio support entry develop/dev-guide-third-party-support.md	The GUI support table lists LibreDB Studio at version 0.13.4 with Full support and no tutorial.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c0f27

This PR only adds LibreDB Studio to the supported GUI tools documentation list and does not change product behavior or runtime configuration; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding LibreDB Studio to the supported GUI tools list.
Description check	✅ Passed	The description covers the change, affected TiDB versions, verification steps, reference link, AI involvement, and applicable change categories. It is complete enough for review.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}