Hello all,

I have existing tables in a database, in a star schema.

I would like a visual tool to create a query joining all tables of the star schema.

Can I do this with Vertabelo ?

Thank you very much

I would like to start using this product, but the models that I create here will reveal privileged, proprietary information about my clients, so I need to be comfortable with the associated privacy.

How are the models secured, what assurances do I have as to the privacy of my models?

I have the licence for vertabelo but still, when I generate my png it is showing watermark . how to remove that?

Hi, I've made a login in Vertabelo with my e-mail account, event bought the SQL complete course and made some lessons, but now, when I tried to login again, the plataform says that my user doesn't exist. Can someone plese, help me? 

Thanks, 

How should I handle array data types from Postgres 9.2 in Vertabelo. 

- Can I declare them visually?

- Can I create indexes on them?

- If not, is there a workaround.

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