Your feedback is highly appreciated! Let's make Vertabelo even better.

+5
Under review

Triggers

mark leavesley 9 years ago updated by Chad P. Prince 6 years ago 2
I've seen the workaround to add computed columns but it doesn't show graphically that the column is computed. Likewise, I could do the same for triggers but again I wouldn't be able to see at a glance where the triggers were. I would have thought another box like you have for default value etc would suffice. If you don't want to make an interface to build triggers fine, but at least allow us to mark that a column has update/insert/delete triggers or is computed.
0
Fixed

Postgres migration does not specify schema in DROP INDEX command

Chase Roden 6 years ago updated 6 years ago 5

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:


Image 743

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

Image 745
0
Planned

Postgres: Access method "gin" does not support ASC/DESC options

Chase Roden 6 years ago updated by Adam Mościcki 6 years ago 1

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

Image 739

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

+2

Add option for PRIMARY KEY that is NONCLUSTERED

Dixant Rai 6 years ago 0

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)
);
0
Under review

NONCLUSTERED PRIMARY KEY

Dixant Rai 6 years ago updated 6 years ago 5

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.

0
Under review

why should i upgrade my account if i am a student?

Natalia Górecka 6 years ago updated by Mariusz Zakrzewski 6 years ago 2

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.

0
Fixed

The product is unusable and keeps crashing. Please resolve it.

Sarfraz Nawaz 6 years ago updated by Rafał Strzaliński (Senior Engineer) 6 years ago 2

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

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

0
Under review

Rename highly buggy

Chrisjan Wust 6 years ago updated by Adam Mościcki 6 years ago 3

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.