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

Include more information about optimising ORM performance

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞

调研方向

Start by reading pull request 201 and its new ORM performance section. Review the listed PartialMatch, ExactMatch, indexing, and filterByCallback examples, then seek community feedback for additional ORM performance practices. Done means the section contains useful, vetted examples and clearly addresses the agreed scope, including whether Elemental documentation belongs there.

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

描述

affects/v5 impact/medium type/docs

https://github.com/silverstripe/developer-docs/pull/201 adds a new section about ORM performance. It doesn't have much in it right now, but there's probably a lot that we can include in here.
Examples:

  • using PartialMatch filters makes indexes effectively useless for that column in that query - so for things like searching for pages in the CMS site tree, swapping to use ExactMatch on title only and adding an index on title will make that query way faster
  • dnadesign/silverstripe-elemental overrides how sitetree search works and adds a super un-optimised filterByCallback() to that query (though its debatable whether elemental docs should be part of the main docs)

We should seek feedback from the community about what they're doing to improve performance of the ORM specifically and include good examples in the ORM performance section (pssst if you're reading this and have any suggestions of what we could add, please add a comment below).

主要语言
没有语言数据
星标
7
派生
76
平均合并
1 天 12 小时
30 天内合并 PR
4

环境准备

从这里开始

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

silverstripe/developer-docs 的其他 Issue

查看 silverstripe/developer-docs 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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