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
Clicking "Create new index" more than once will add duplicate icons for that field. Then, when deleting this field, it is not actually deleted and still exists in the background. Not sure whether this false delete is related to how it has been assigned duplicated index types.
Steps to reproduce the behavior:
Add a field in a table and give it a name
Assign an index to it e.g UNIQUE
Repeat step 2 with the same index type - now the icon is duplicated
Delete the field
Add a field again and name it the same as in step 1
The previous field that was deleted now seems to come to life again as the previously assigned indexes show again
Expected behavior
The field should only be allowed to be given an index type once, i.e. the icon should not be duplicated. Further, when deleting the field, it should not still exist in the background - this false delete may be related to the duplicated icons.
Application (please complete the following information):
Version 0.4.2
.exe install
Desktop (please complete the following information):
OS: Windows 11
Version 21H2
The text was updated successfully, but these errors were encountered:
Hi Jason,
thanks for you report.
The part related to same icon multiple time its not a bug because you can have more than a key on a field, for example in the case of indexes related to multiple fields.
The bug is when a field is deleted and its keys aren't cleared from the tab memory.
disqit
changed the title
Duplicated 'Index' icons for fields and improper field deletions
Index keys not cleared from tab memory
Jan 26, 2022
Clicking "Create new index" more than once will add duplicate icons for that field. Then, when deleting this field, it is not actually deleted and still exists in the background. Not sure whether this false delete is related to how it has been assigned duplicated index types.
Steps to reproduce the behavior:
Expected behavior
The field should only be allowed to be given an index type once, i.e. the icon should not be duplicated. Further, when deleting the field, it should not still exist in the background - this false delete may be related to the duplicated icons.
Application (please complete the following information):
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: