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

Incompatibility of new DB structure and dbcopy #924

Open
fm-maniac opened this issue Feb 2, 2023 · 0 comments
Open

Incompatibility of new DB structure and dbcopy #924

fm-maniac opened this issue Feb 2, 2023 · 0 comments

Comments

@fm-maniac
Copy link

With the new DB structure omitting the consecutive ID and using the combination of timestamp and channel_ID as the primary key, dbcopy does no longer work for DB backups.

dbcopy requires a single primary key -> iterative (partly) backups fails. Full backups are always aborted after 1000 data sets.

Unfortunatly new installs of the middleware come with the new DB structure.

In general omitting the consecutive ID is welcome in terms of data efficiency. But then dbcopy needs to be updated too.

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

No branches or pull requests

1 participant