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

QuantityValue webservice bugfix #3372

Merged
merged 1 commit into from Sep 25, 2018
Merged

QuantityValue webservice bugfix #3372

merged 1 commit into from Sep 25, 2018

Conversation

markus-moser
Copy link
Contributor

A check is needed whether the unit actually exists otherwise a problem will result if units get deleted as the unit ID might be still in the database.

…ctually exists otherwise a problem will result if units get deleted
@brusch brusch added this to the 5.5.0 milestone Sep 25, 2018
@brusch brusch added the Bug label Sep 25, 2018
@weisswurstkanone weisswurstkanone merged commit 2c8aa67 into master Sep 25, 2018
@weisswurstkanone
Copy link
Contributor

Many thanks, maybe we should also think about a proactive cleanup task as part of the maintenance?

@markus-moser
Copy link
Contributor Author

yes, the cleanup task might be a good idea

@dpfaffenbauer
Copy link
Contributor

or just use foreign key constraints?

@weisswurstkanone
Copy link
Contributor

technically possible, was considering this but wasn't sure if this really performs ...

@dpfaffenbauer
Copy link
Contributor

@weisswurstkanone
Copy link
Contributor

maybe open a seperate "improvement" ticket ?

@dpfaffenbauer
Copy link
Contributor

of course, either for the foreign key or the cleanup task. Can you?

@weisswurstkanone
Copy link
Contributor

done, see #3376

@markus-moser markus-moser deleted the quantityvalue_fix branch September 26, 2018 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants