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
@1ilit is there a reason why some types don't allow the default value to be set at all? it seems rather arbitrary to me, for example, to disallow JSON columns from having a default value set, since that should work on most if not all database engines. I talked about this in the PR, though I'm not sure if you saw it: #339 (comment)
Describe the bug
When creating/editing a table with a UUID column, it is not possible to set it's default value because it is disabled.
To Reproduce
Steps to reproduce the behavior:
id
column type to UUIDExpected behavior
I expected to be able to set the default value for the UUID type, i.e.
gen_random_uuid()
.Screenshots
Desktop (please complete the following information):
Additional context
Also, it seems that the cursor for
:disabled
elements is wrong:This is what it's probably supposed to look like:
(or unset so it inherits the cursor style from it's parent div)
The text was updated successfully, but these errors were encountered: