Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

perf(catalog): ERD neighbourhood and MCP describe/sample read the whole schema catalog; filter tables in SQL

未关闭
#1,572 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
dart, mysql, postgresql, sqlite

调研方向

Start with lib/core/erd/erd_catalog.dart:198-248 and lib/core/mcp/mcp_query_service.dart:245-270, then inspect the columnsSql and viewColumnsSql definitions for PostgreSQL, MySQL, and SQLite. Trace how ERD neighbourhood names and MCP table validation flow into those queries, and review the related tests. Done means SQL filters catalog reads to the requested tables, MCP uses a cheap existence check where appropriate, and a neighbourhood remains complete beyond the catalog row limit.

由索引模型根据 Issue 内容生成。

描述

backend core P3 performance

Problem

Two paths read the whole schema catalog when they need a few tables:

  1. ERD neighbourhood (ErdCatalog.loadNeighbourhood, lib/core/erd/erd_catalog.dart:198-248). It loads all FKs (needed for the graph walk), then for every schema in the neighbourhood runs columnsSql for all columns of that schema and filters in Dart (if (names.contains(r[0])), :230/:238). The PostgreSQL columnsSql has per-column correlated subqueries (unique-index EXISTS, pg_enum string_agg, col_description, pg_get_expr), so the cost grows with the schema, not with the diagram. With catalogRowLimit = 200000 (:19) a large schema is truncated before filtering, so the focused table can lose its columns even though it needs only a few rows.
  2. MCP describe_table / sample_rows (McpQueryService._loadCatalog, lib/core/mcp/mcp_query_service.dart:245-270). To find one table it runs three catalog queries over the whole schema (columns, FKs, view columns) on every call. sample_rows uses the result only to validate the table name.

Fix

  • Add a table filter to columnsSql / viewColumnsSql: PostgreSQL c.relname = ANY($names) per schema, MySQL table_name IN (...), SQLite m.name IN (...) (literal-escaped as in _lit, or bind parameters where the delegate supports them).
  • ERD neighbourhood: walk FKs first, then fetch columns only for the resulting names.
  • MCP: validate the name with a cheap existence query (to_regclass / information_schema.tables / sqlite_master), and describe one table with the filtered column/FK queries. Keep the full catalog only for list_tables and the schema:// resource.
  • Tests: the generated SQL contains the filter; the neighbourhood of a table in a schema larger than the row limit is complete.

Related: ERD epic #1166 and #1167 (same catalog SQL).

主要语言
Dart
星标
23
派生
1
平均合并
31 分钟
30 天内合并 PR
570

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。