If you build a create table script for SQL Server, it fails to run; "ON PRIMARY" is added at the end of all indexes, tables, etc.  - since "PRIMARY" is a reserved word, the script won't work.

Changing the script from "ON PRIMARY" to "ON [PRIMARY]" fixes the issue; could this be done at point of generation?

Right now, in order to select more than one object from the diagram, I can only use the "select area" tool.

In most desktop applications, new objects can be added to selections by clicking "Ctrl" and the mouse button at the same time.

Ideally, "Ctrl" and the "select area" would then add new areas to the existing selection.

A revision history of changes made to a model (and regression to a previous version) would be an incredibly useful feature for developers.

Specifically, if you share a model with another user (as a viewer only), they should be able to open the model without registering for a premium account

hi if anyone set a filed name date-time for example i set EnterDate-Time the vertabelo accept this and when i export sql and import on query the sql occured error
"Incorrect syntax near '-'."
i think it is better that Vertebelo Prevent to register a field that contain - 
for example mo-date 
cant be save on vertebelo 

I've recently used this very useful feature here:
http://www.vertabelo.com/blog/documentation/revers...

I found that there were a bit too many manual steps to importing a schema. All I'd like to enter is JDBC-URL (or some non-JDBC connection format), username and password and be done.

If you take DBeaver for instance (http://dbeaver.jkiss.org), it will even automaticall download the JDBC driver if applicable.

I guess this kind of functionality could be implemented in Vertabelo via a Java Web Start application, or via an applet (?) or via a Chrome Plugin...

Hi, I see this bug http://awesomescreenshot.com/0de3gdyv66
P.S. sorry for my english.

When primary key is checked, the nullable column checkbox is greyed out.

This is all well and good if the nullable column is blank, but if it is checked as well, it makes it difficult to resolve the inconsistency (one has to uncheck PK, uncheck N, then re-check PK).

Suggest that either nullable checkbox should *not* be greyed out if it is checked, or alternatively that any action to check the PK field should uncheck nullable.

Hello, 
I see a warning in my model that says:
"Type is not supported by chosen database engine"

It refers to a field that is of type uritype(256).  We have checked Oracle 11g reference guide and it is supported.  See this reference link for 11g:
http://docs.oracle.com/cd/B28359_01/appdev.111/b28...

Thanks,

John