This is a big error. In mySQL, if you have same constraint name but different capitalization, it is still the same thus producing error. Meanwhile, at the database maker, it is possible to remove the error of having same name by simply changing the case of the other constraint. Vertabelo should produce error if you have same name in constraint whether it is case different.

Instead of adding a column of tableName_ColumnName just add ColumnName or at least make it configurable

I would like to see the alternate keys on the diagram

Can you help me change my account type so I can import SQL Scripts

Thanks

When I define about 30 columns in a view, adding next columns takes long time - 10 seconds or more. This makes working with big views very inefficient if not impossible.

I am trying to enter view columns quickly. But I cannot.

1. I click on 'Add column'
2. I enter column name
3. I press TAB
4. Focus is lost somewhere in space, instead of moving to neighbouring column type input.

The search box in Diagram Editor is slow, and responds after several seconds of waiting.

Additionally, it stops working from time to time.

I am new to database design and there are many terms in the right properties pane that I do not understand. I was looking for an explanation of how to use the cardinality settings and your knowledge base came up a bit short for someone just starting like me.

Here is a link to a youtube video that helped me understand the concept and symbols

You might add more to your documentation on what each property does. So far however, I am very pleased with how easy it is to use your product and how much I have learned in a short time.