When I generate a migration that modifies an index in Postgres, the generated SQL does not specify the schema for the index on the DROP statement and therefore fails. In this example I changed WHERE clause on an index:

The resulting DROP INDEX command does not work unless the schema is specified:

Users should be able to create PrimaryKey tha is NONCLUSTERED. While PK flag to identify them the default should be CLUSTERED (as is the case in most RDMSs) but an option should be available to be able to create a NONCLUSTERED one as well. The resultant DDL script should result in this.

CREATE TABLE sample_table (
   sample_column int  NOT NULL,
   CONSTRAINT sample_table_pk PRIMARY KEY NONCLUSTERED (sample_column)
);

Oops we've got a problem. Something went wrong ... Reload page

I get the above error message and I loose all my changes.

Hi, when trying to import data model info for mariadb database, I cannot get all of the tables recognized regardless of sql tool used for export.  Trying to use MySQL option - perhaps a MariaDb specific driver is needed?  

My account says that my trial expired even though I used my university e-mail to create my account. Can I please get it sorted. I really need vertabelo for my Data Base Systems module. 

For the printing of models, it would be very interesting to have the option to choose just print PK and FK or All the columns of the tables, since for large models, it is not displayed well.

If a Data Model is drawn, is there an easy way to convert to DFM or DV 1 or 2.0?

Thanks

float is currently missing for MySQL