Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

able to initialize and not initialize demo data in invoke resetdb #20

Open
wants to merge 1 commit into
base: 17.0
Choose a base branch
from

Conversation

reichie020212
Copy link
Member

@reichie020212 reichie020212 commented Feb 12, 2024

To initialize a new empty database with demo data, use below invoke command

invoke resetdb --demo

To onitialize a new empty database without demo data, just remove the --demo

invoke resetdb

@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Feb 12, 2024
Copy link

sonarcloud bot commented May 28, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link
Contributor

@kneckinator kneckinator left a comment

Choose a reason for hiding this comment

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

@reichie020212 in the PR description, or in relevant documentation files, can you please provide an invoke command line showing how the new option is used?
Thanks.

@reichie020212
Copy link
Member Author

@reichie020212 in the PR description, or in relevant documentation files, can you please provide an invoke command line showing how the new option is used? Thanks.

@kneckinator done updating the PR Description.

@kneckinator
Copy link
Contributor

@kneckinator done updating the PR Description.

Thanks. Note, however, that this changes the previous default of the invoke resetdb command as odoo-click-initdb which is used to prepare the database defaults to --demo if the parameter is omitted.

We have two options going forward:

After some consideration, I prefer the first solution of keeping this PR "as-is" and updating the documentation, as adding the --demo to the documentation conveys to the reader that there is such as thing as "demo data" that can be selectively applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants