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

Query time issue with "Tag" implementation

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

@zakriya057 已经在做这个了。

开始于 2024年12月2日。

评估

这个 Issue 还没有评估数据。

描述

enhancement feature proposal medium priority

Our current Implementation of tag's associated with a Shift is done via django-taggit here.
This implementation is somewhat lazy and causes a lot of overhead when querying all shifts
via the /shifts endpoint.
I have already created a branch in which django-silky is installed to profile the endpoints see the profiling branch.

Tags are a convenience feature for users to categorize Shift s and also sort them in a manner. Due to the nature
of how django-taggit implements Tags (ContentTypeRelations/Own db table) we are creating one query per shift object
as we are querying Shifts.

Main Issues:

  1. Huge Query overhead
  2. Somehow, if a new Shift has a Tag that is already existing, it is not reused but a new one is created (Not 100%, needs checking)

Goal:
Find a way to implement Tags in a way that the over head is reduced/eliminated. Possible changes in the Frontend are acceptable.

Check if Tags are reused.
If Tags are NOT reused, implement reusing them.

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

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

ClockGU/clock-backend 的其他 Issue

查看 ClockGU/clock-backend 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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