You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: