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:

When I create an index that uses the GIN access method, Vertabelo requires me to choose ASC or DESC:

-- which GIN does not support. So the generated SQL DDL says (e.g.):

CREATE INDEX test_table_idx_1 on schema.test_table USING gin (column_2 ASC);

If I don't manually remove the "ASC" from generated code, Postgres will not run the statement, returning

access method "gin" does not support ASC/DESC options

I would like to be able to unset the ASC/DESC option and have the generated SQL not include the index order when it's not compatible with the access method, so that the generated SQL looks like:

CREATE INDEX test_table_idx_1 on schema.test_table USING gin (column_2);

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)
);

Is it possible to create NONCLUSTERED PrimaryKey while still using the PK flag to identify them? I'm trying to achieve this in sql server.

I heard that being a student helps you to have more upgraded account than normal user. Though, i cannot do more references because it says i dont have upgraded my account. Could anyone tell me why is like that? I have a project to do for my university programme and they asured me it will be free and upgraded.

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

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

I'm having problems with renaming a diagram (or "physical data model"). My new tables randomly get renamed to one specific old diagram. These new tables are copies of the old diagram (or copies of copies, which might go under a different name). Have tried renaming in the folder view or in the model details view for specific diagram, logging in/out, various combinations of logging in/out with opening/not opening the diagrams and different browsers.