Issue between endpoint_route_handler and database_cleanup

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
python
领域
database

调研方向

The issue reports that the database_cleanup step drops the endpoint_route table because it is not declared as an Odoo model. Start by reading how the module declares its models and how database_cleanup decides which tables to remove, then check the maintainer's earlier change that introduced endpoint_route. Done means either a decision from the maintainers on whether endpoint_route should be protected, or a patch that keeps the table while hiding it from users. Agree the approach in the thread before coding.

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

描述

bug

After a major Database migration, I decided to pass database_cleanup to remove fields and unnecessary models.

However, I found that the system deleted endpoint_route table because it is not defined as an odoo model

@simahawk as you did the change, there is a reason for not using Odoo tables? Can I make a change to include this table where users will not be able to access?

主要语言
Python
星标
49
派生
124
平均合并
4 天 13 小时
30 天内合并 PR
11

环境准备

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

从这里开始

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

OCA/web-api 的其他 Issue

查看 OCA/web-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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