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

If you're editing the reference name or description and press Enter, a new PK/FK reference is added to the table below. This is unexpected behavior.

Under Reference Properties, the PK/FK table has two design decisions that make it less intuitive.

The first is that the form fields for creating a new relationship are shown *before* rather than after the existing relationships. The second is that the form pre-populated with values, and fields have a much lighter color than the extant rows of the table.

Combined, it is visually unintuitive to easily see the existing relationship(s).

Suggest using a different color for the existing rows, or a bold font, moving the blank form below any existing rows, and dimming the form fields.

small typo in one of the popups

Currently its not possible to define indexes that use a sub length of a column. This is often used for char and byte type fields that are very long.

In mysql you can do the following

    CREATE INDEX part_of_name ON customer (name(10));

It seems that only one diagram is allowed per model.  For large databases, having a single diagram does not work so well.

Why can't you allow creating multiple diagrams for a single model.

Also, subject areas does not work as well, because they require related tables to be close to each other within a diagram.

With multiple diagrams, you can create diagrams specific to some topic and still use subject areas to group tables within the diagram.

Thanks!

Please, alway show scrollbar in columns section because when I use this section for table that have a few column I found a problem.
First I expand column's property by click arrow down button that make scroll bar appear and delete button moved.
Then I want to collapse this column's property without move my mouse so I hit the moved delete button.