Please support standard Undo + Redo Keyboard Shortcuts. CMD+Y is very odd, not intuitive, and causes mistakes thinking a redo was applied when it is not. It's easy to lose work due to this non-standard CMD+Y shortcut.

STANDARD

CMD+Z = Undo (works)

CMD+SHIFT+Z = Redo (does not work)

In Additional SQL Scripts, I've made changes to add new types used in the model. However, generating a migration does not include these changes and requires manual analysis to modify the migration script.

How can a migration be generated that includes changes to types?

CREATE TYPE billing_interval AS ENUM (
'once',
'monthly',
'yearly'
);

I am trying to renew my account, which lapsed, but it will not allow me to remove users or select a smaller plan. I am on the only one at our company who wants to use Vertabelo, so I don't need the old plan. I hope to change that down the road, but I need to be able to use it myself first. Can you help me remove those users or purchase a smaller plan somehow?

I have Big Data infra with a clickhouse attached and wanted to know if the tool supports that ?

I want to start by saying that the system is excellent, I just found a bug and I'm glad to tell you about it, so I contribute to its better functioning ...

Bug: When I try to delete a folder it is throwing me a javascript error ...

Hi there!

I generated a migration SQL script for Postgres physical data Model, but it didn't work properly.

One of the changes was setting a default for a timestamp column, using now() function as the default value.

The ALTER TABLE command generated by the migration feature was:

-- Column: created_at.
ALTER TABLE rq_forms
ALTER created_at SET DEFAULT 'now()';

However, it creates the default with a fixed timestamp, the date and time of the ALTER TABLE execution.

The expected behavior was setting now() function as the default, not the fixed date and time.

This is the correct script the migration feature should generate: 

-- Column: created_at.
ALTER TABLE rq_forms
ALTER created_at SET DEFAULT now(); --> Without the single quotes.

Just to mention, the CREATE TABLE is working fine, setting the now() function properly when I generate the SQL Script for the same table in the model as seen below. Just ALTER TABLE generated by the migration has the bug.

-- Its OK!

CREATE TABLE rq_forms (
id serial NOT NULL,
created_at timestamp NOT NULL DEFAULT now(),
updated_at timestamp NULL,

(...)

One more request:

Vertabelo could have the type "timestamp with time zone" in the Type windows predefined options (in the Date and time section).

The "timestamp" option creates a "timestamp without time zone" column.

It would be nice to have the option to choose between with or without time zone in Vertabelo.

I hope I could help improving Vertabelo.

Regards,

Fernando dos Santos.

I do not see the three reference types in the Model Structure panel. How do I add them?

Hello,

My company has build a large database on Amazon, but the Data Engineer do not have database model.

Thus, as a data analyst, it is very hard for me to understand the database without database model (diagram) or any document.

Can I use Vertabelo to do reverse engineering to generate database model (diagram) from existing database?

The import SQL parser seems to not like `gen_random_uuid()`(supported in Postgres 13) when that is set as the default. It is also failing to parse`timezone('utc'::text, now())`(supported in Postgres 13).

I've been resorting to deleting these from my sql file just so I can get the table to import.

Example:

CREATE TABLE public.skill (
    title character varying NOT NULL,
    description text,
    id uuid DEFAULT gen_random_uuid() NOT NULL,
    created_at timestamp without time zone DEFAULT timezone('utc'::text, now()) NOT NULL,
    updated_at timestamp without time zone DEFAULT timezone('utc'::text, now()) NOT NULL,
    deleted_at timestamp without time zone
);

To get it to import I have to delete those:

CREATE TABLE public.skill (
    title character varying NOT NULL,
    description text,
    id uuid NOT NULL,
    created_at timestamp without time zone NOT NULL,
    updated_at timestamp without time zone NOT NULL,
    deleted_at timestamp without time zone
);

Would be nice to have the import accommodate these functions so I don't have to keep editing my sql files before import.