Skip to content

Conversation

@dvuckovic
Copy link
Contributor

No description provided.

@dvuckovic dvuckovic requested a review from ralf401 October 27, 2025 11:37
@dvuckovic dvuckovic self-assigned this Oct 27, 2025
@dvuckovic dvuckovic linked an issue Oct 27, 2025 that may be closed by this pull request
@github-actions
Copy link

github-actions bot commented Oct 27, 2025

Artifacts

Produced during runtime

📦 epub-f420c49
📦 html-f420c49
📦 htmlzip-f420c49

Copy link
Contributor

@ralf401 ralf401 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, assuming the commands are working and the truncate creates a new database so they can be migrated afterwards ;-)

Just one minor thing you could take into consideration (was of course missing before too): Add a short "intro" on top of each command (e.g. something like Delete and re-create database:)

@dvuckovic
Copy link
Contributor Author

@ralf401 Yes, truncate will actually clean up the existing schemas in the database, instead of dropping it. This is needed because when we drop the database, Zammad DB user from package installations has no privileges to recreate it, therefore rendering some helper commands useless.

Thanks for the review, I added short command descriptions above each block.

@dvuckovic dvuckovic merged commit 0ac818b into pre-release Oct 27, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adjust reset instructions to refer to the new command

3 participants