-
Notifications
You must be signed in to change notification settings - Fork 53
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
Dangling reports left when bug delete #17
Comments
Which database do you use? I could not reproduce this issue. |
MariaDB 10.1.26. |
I'm using MariaDB 10.1.34, so it's probably a configuration issue. My first idea would be a wrong dialect: Did you put |
Hah, no, I was using (I previously had to set things manually to use utf8 instead of utf8mb4, because of column width errors. I wonder if setting the proper dialect would have fixed that as well.) |
It still appears to be broken. Steps:
|
Still can't reproduce. Please post the output of |
|
Ok, there's the issue. Here is how it should look like:
Basically, you're missing the foreign key reference. Now the question is: why? Could you create a new database and initialize it with the correct dialect to check if it works there? |
Same symptoms as before, after a full wipe and refresh, using the correct dialect.
|
So I was finally able to reproduce it, and it was caused by a typo. |
I recommend to
But you could also add the constraint manually. |
Just did exactly that. |
When deleting a bug, it looks like the reports previous associated with the bug are not deleted, remaining in the database, but there is no longer a way to access them, so they're just leftover data. Probably these reports should be deleted when the associated bug is deleted.
The text was updated successfully, but these errors were encountered: