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
Describe the bug
The Random > UUID automatic generation option isn't showing up when valorizing fields of UUID type (on Postgres) or of Binary(16) type (on MariaDB).
To Reproduce
Steps to reproduce the behavior:
If on Postgres, create a table with a field of UUID type; if on MariaDB, create a table with a field of Binary(16) type
Open the table and click on "Insert rows"
See the dropdown next to the input field displaying the "Manual value" option only.
Expected behavior
The dropdown should display the Random > UUID option too.
Application (please complete the following information):
App client: PostgreSQL / MariaDB
App version: 0.5.15
Installation source: AUR
Environment (please complete the following information):
OS name: Manjaro
OS version: 21.3.7
DB name: PostgreSQL 14.4 / MariaDB 10.7.3
The text was updated successfully, but these errors were encountered:
I just implemented the PostgreSQL UUID. As far as MariaDB support is concerned, it is different and I need to do some refactors and improve the modification of binary fields, so it is something I will implement in the future.
As far as MariaDB support is concerned, it is different and I need to do some refactors and improve the modification of binary fields, so it is something I will implement in the future.
No problem. PostgreSQL's UUID was (at least for my use) the most urgent one. MariaDB's one, while it would be an useful addition, can wait.
Describe the bug
The Random > UUID automatic generation option isn't showing up when valorizing fields of UUID type (on Postgres) or of Binary(16) type (on MariaDB).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The dropdown should display the Random > UUID option too.
Application (please complete the following information):
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: