The UUID datatype for PostgreSQL is missing and is valid in 9.0+ versions.
It is just missing on the list but you can type it.
I decided to try Vertabelo out because I liked a lot of the features that were described on the product pages and the blog.
After I successfully managed to get my schema imported, I noticed that all my tables and views that use the type UUID
are showing up with validation errors because UUID is not a recognized type.
I found this support ticket from seven years ago but it doesn't mention the fact that it causes validation errors.
Is this just not something that will be fixed? It seems like it would be extremely straightforward to update the list of valid types for PostgreSQL.
This type is not on list in UI type control by design as this not used so often. However it shouldn't give validation errors as you type this manually. Please see sample design on the picture below, where UUID type is in sample table without any validation errors.
Could you please
provide the sample of your model that doesn't work that way.
The error is caused when performing a reverse engineering of a schema. The types that are not recognized by Vertabelo have a suffix of a number in parenthesis that causes the error to appear.
I was able to go in to every table and change the type fields to remove that suffix and it cleared up the errors, but it was rather manual and time consuming.
Thank for providing the context. We will add the issue with reverse engineering to our backlog. So I close this issue as it is related to different context.
Customer support service by UserEcho