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

Database schema changes

未关闭
#54 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
sql
领域
backend, databases

调研方向

Start with docs/setup.sql and reproduce the reported SELECT against a large items table to understand the current schema and query cost. Review the feeds, items, and subscriptions definitions, then trace the application code that uses feedUrl; done means the integer feedId migration and related queries remain synchronized across all three tables.

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

描述

Seeing that a database with millions of rows in the items table, can get queries to slow down, specifically this one:

SELECT * FROM items WHERE flDeleted = FALSE AND feedUrl IN (SELECT feedUrl FROM subscriptions WHERE listName='dave') ORDER BY pubDate DESC LIMIT 175;

Which can take ~10 seconds to load, I propose we switch from using feedUrl as the primary key to an integer based key, which will help speed up the query significantly. Testing locally, the same query took about ~20ms after the switch.

Maybe for such a big change, we might as well review the setup.sql file. The following tables use feedUrl as primary key and should be changed:

  1. feeds
  2. items
  3. subscriptions

But this will also involve code changes to keep in sync the new feedId with the current feedUrl and querying feedId instead.

主要语言
HTML
星标
11
派生
4
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

scripting/feedlandInstall 的其他 Issue

查看 scripting/feedlandInstall 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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