Your feedback is highly appreciated! Let's make Vertabelo even better.

  1. Форум: Vertabelo
+1

Disabling "scroll to zoom" doesn't stick and it should be off by default

Terris Linenbach 1 год назад • обновлен 1 год назад • 2

The instructions in https://support.vertabelo.com/communities/1/topics/185-disable-scroll-to-zoom don't work. If you click on the gear icon again and go into the settings, the "scroll to zoom" checkbox will still be checked. This happens in edit and view modes. This annoying feature should be disabled by default in my opinion. Scroll should scroll, not zoom.

0
Запланирован

Add 75% Zoom

Terris Linenbach 1 год назад • обновлен 1 год назад • 2

The zoom drop-down levels are 25-50-100-200 and 400 .. I often want 75. I never want 400.

0

small mistake or small bug

Xasanboy Isxoqov 1 год назад • 0

Image 1404

Hi, I would like to ask you to look at the output from the code I wrote. It would be good if you could check the output in your table, it seems wrong. Please let me know if I am wrong.

0
Отвечен

The take control feature is taking hours to load

Giorgos Geroukos 2 года назад • обновлен s rapport 1 год назад • 2

Whenever I try and take control of my physical data model, it takes hours to happen. Is there any way to fix this

0
Отвечен

cardinality

philippe bissohong 10 лет назад • обновлен Emily Webster 1 год назад • 3
how can i show cardinality in the model. I can only see min and max on one side of the relationship.  Example: ||-----|< as oppose to  |-----|<

Thank you,
Philippe
+27
На рассмотрении

Pattern for naming objects

Aleksandra Machewka 10 лет назад • обновлен fed 1 год назад • 3
It would be a handy feature to allow user to define patterns for default object names, eg. primary keys. Currently, PK is formed using pattern "{objectName}_pk". Such pattern could be defined by user, having access to variables like {objectName}, {objectNameSingular} (for objects named in plural form). For FK, source and destination object names could be accessible, so user can form default FK name as "FK_{sourceObjectName}_{destinationObjectName}". I'm aware, that this can be done via explicitly naming PKs and FKs, but such feature would be useful when model is big and many relations exist.
0

Feature request: Share a model to my team

Terris Linenbach 1 год назад • обновлен 1 год назад • 0

I would like to share models to the whole team without specifying individual email addresses. The team of course changes when I add and remove team members.

+14

PostgreSQL enum types

kspar 7 лет назад • обновлен Terris Linenbach 1 год назад • 1

Please add support for PostgreSQL enumerated types.


Is there a workaround that enables at least modeling/showing enums graphically somehow without proper code generation support?

0

Share models across licenses?

John Chapman 1 год назад • 0

My team and I use Vertabelo for our internal design work.  I have a customer that wants models of their new data warehouse built for them that they will then take ownership of after the work is complete.

If I create models under my license structure, can I transfer (copies) of those diagrams to them that they could then maintain in their own licensed version?



Сервис поддержки клиентов работает на платформе UserEcho