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

Initializing a bridge deletes the database #15

Open
Paula-Kli opened this issue Dec 21, 2021 · 1 comment
Open

Initializing a bridge deletes the database #15

Paula-Kli opened this issue Dec 21, 2021 · 1 comment

Comments

@Paula-Kli
Copy link
Collaborator

For sensors and actuators the database gets deleted when initializing a bridge with an id that was seen before. In that way we do not risk assosiziating non existing sensors with a bridge which might have different and new sensors and actuators.

At the moment the sensorfeeds do not get deleted by cascade which might be good to store the data for later or bad since we do not know which datatype the values have if we delete the assoziated sensor value in the database. But the bridge will initialize all the sensor again anyways.
(it also prevents us from overflowing and getting ids higher than 253 after initializing the same bridge several times see also #14

@Paula-Kli
Copy link
Collaborator Author

Update from 6a94887 :
we delete the sensorfeeds since postgresql does not allow them to stay but it happens manually and not by the database cascade

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