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

[BUG] Can't set Default value for UUID type #338

Closed
HeCorr opened this issue Feb 2, 2025 · 1 comment · Fixed by #339
Closed

[BUG] Can't set Default value for UUID type #338

HeCorr opened this issue Feb 2, 2025 · 1 comment · Fixed by #339

Comments

@HeCorr
Copy link
Contributor

HeCorr commented Feb 2, 2025

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:

  1. Open web editor
  2. Choose a database (i.e. PostgreSQL)
  3. Add a new table and expand it's details
  4. Set id column type to UUID
  5. Show column details (···)
  6. Attempt to change the Default value field

Expected behavior
I expected to be able to set the default value for the UUID type, i.e. gen_random_uuid().

Screenshots

Image

Desktop (please complete the following information):

  • OS: Linux
  • Browser: Brave

Additional context

Also, it seems that the cursor for :disabled elements is wrong:

Image

This is what it's probably supposed to look like:

Image Image
(or unset so it inherits the cursor style from it's parent div)

@HeCorr
Copy link
Contributor Author

HeCorr commented Feb 3, 2025

@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant