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 摘要。