langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

When dify releases the version, it can publish the ddl statements related to database adjustment into a separate file #11106

New Issue
Closed
opened 2026-02-21 18:54:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:54:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @leeyisoft on GitHub (Mar 14, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When dify releases the version, it can publish the ddl statements related to database adjustment into a separate file, so that I can know which fields need to be modified when I upgrade, and not know where to adjust until I report errors (I am started based on docker, or you have other solutions to automatically upgrade the database).

2. Additional context or comments

I started to deploy dify locally based on docker from 0.12.1;

"workflow_app_logs" "workflow_node_executions" "workflow_runs" three tables in the database used for a period of time occupied a large amount of disk space. After manually deleting the records in the tables, the database disk space was not released. Finally, I used pg_repack to solve the problem

Some time ago, I upgraded dify to 0.15.3, and I upgraded it according to the upgrade instructions of docker installation on github. After that, I found that many data structures were incompatible, which took a lot of time

Recently plan to upgrade to 1.0.1, because of busy work dare not speak time to try, here send a help

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @leeyisoft on GitHub (Mar 14, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. When dify releases the version, it can publish the ddl statements related to database adjustment into a separate file, so that I can know which fields need to be modified when I upgrade, and not know where to adjust until I report errors (I am started based on docker, or you have other solutions to automatically upgrade the database). ### 2. Additional context or comments I started to deploy dify locally based on docker from 0.12.1; "workflow_app_logs" "workflow_node_executions" "workflow_runs" three tables in the database used for a period of time occupied a large amount of disk space. After manually deleting the records in the tables, the database disk space was not released. Finally, I used pg_repack to solve the problem Some time ago, I upgraded dify to 0.15.3, and I upgraded it according to the upgrade instructions of docker installation on github. After that, I found that many data structures were incompatible, which took a lot of time Recently plan to upgrade to 1.0.1, because of busy work dare not speak time to try, here send a help ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:54:58 -05:00
yindo closed this issue 2026-02-21 18:54:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#11106
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?