I am on my 5th day trialling Vertabelo. I have a diagram with about 90 entities - not large, not small.

I want to move to a paid subscription because I want to expand the team of collaborators.

Yet the latency in the UI is a problem.  It takes a long time to register clicks and zooms.

I use Figma constantly and it is buttery smooth on my machine, so its not my machine or my network connection.

Is this latency standard for Vertabelo?  Will it improve when i move to a paid subscription?

Hello,

I wanted to add a member of my team in my Vertabelo team but it seems I cannot because he already has an account.

When I fill the form to add it, it indicate "This e-mail address is already used in another Vertabelo account.".

Is there any workaround? I even don't understand the limitation.

Is seems Vertabelo's Postgres is two version behind. Postgres 15 is required for custom types. When importing scripts that contain CREATE TYPE, model generation is aborted. Also, there is no way to generate models with types that are commonplace in modern Postgres hosing services.

When will Vertabelo support more current versions of Postgres, v15?

More and more tools are using Ctrl+Scroll up/down to manage zoom (currently thinking of Figma, Miro)

and scroll up/down/left/right to manage scroll.

Switching from those tools to Vertabelo is... painful ^^" because when I try to move on a document, it triggers an unwanted zoom 😅

Could you consider making this behavior an option, before eventually making it a default?

Thanks 🍻

While normally I think the "scroll to zoom" feature is great, it can be pretty difficult to use with a Magic Mouse. I've turned it off, but would love to be able to zoom-in/zoom-out with a key command in addition to the control buttons.

It would be very helpful if the folder and files structure can also be shareable. I can share documents but my teammates see them disorganized.

Hi,

When creating an association between two entities, it is not possible to specify the future primary key of the association.

For an 0..N cardinality, the entities identifiers will be added as foreign keys into the association table, but then the physical model must be edited to add the primary key of the associative table.

This will have to be done every time the the logical model is updated.

An alternative way would be able to update a physical model from an existing logical model.

Thoughts ?