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

SYSTEMTOOLS_MYSQLDUMP not updated when db restored to another installation #9086

Closed
torvista opened this issue Jul 10, 2018 · 2 comments
Closed
Labels
Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open

Comments

@torvista
Copy link
Contributor

The first time the database is backed up using the admin tools, this constant is created and stored in llx_const.
eg: C:/xampp.7.2.6/mysql/bin/mysqldump

When this backup is restored to another Dolibarr fileset/another installation, this path becomes invalid and so backups cannot be done/cause an error message.

Once this constant is dropped from llx_const, the backup page re-detects the correct value.

I suggest that the backup page should always check/update the path or indicate not found for the tool.
Otherwise the database is not portable.

@torvista
Copy link
Contributor Author

I delete this by SQL on every restore. Is this constant even necessary at all?

@github-actions
Copy link

This issue is stale because it has been open 1 year with no activity. If this is a bug, please comment to confirm it is still present on latest stable version. if this is a feature request, please comment to notify the request is still relevant and not yet covered by latest stable version. Without comment, this issue will be closed automatically by stale bot in 15 days.

@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open
Projects
None yet
Development

No branches or pull requests

1 participant