When creating a database query, for example in the ‘database delete’, the ‘value’ dissapears when changing the key.
This video shows what I mean:
CleanShot 2023-10-29 at 22.21.17
AFAIK this happens on every “WHERE” database UI element.
A small yet very annoying bug to have happen multiple times a day.
Breaks the flow.
This is actually per design, as you usually want also a different value when using a different key. So leaving the same value will lead to more problems. So when you change the field - then you you also change the value.
Ah I see.
Personally for me this doesn’t work like that but maybe my brain is an outlier.
I often duplicate these actions and have in my mind what I want to do. So I change the key and the value in no particular order. And apparently I very often change the value first, then I change the key, and then I have to change the value again 
Perhaps other people can chime in if this also bothers them? If it’s just me I’ll adjust 