When adding a second entity, I can not move it to a different location  on the design panel, all entities move together.  Secondly creating a relationship by dragging is not work, either nothing happens when dragging the relationship arrow or it creates a relationship to the same entity.  Very from frustrating.  I can not use this tool at this point. 

The zoom drop-down levels are 25-50-100-200 and 400 .. I often want 75. I never want 400.

Hi, I haven't received my confirmation e-mail.
I resent it many times but it doesn't seem to work.

is there any possibility u can help me ?
Thank you.

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.

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.

When creating a new model from an existing SQL DDL script (i.e. Content: "from SQL" is selected), the import fails if the table has a foreign key constraint with no columns listed on the foreign table.  In that situation it should use the primary key for the referenced table as the referenced columns.  Instead I received a cryptic error of ERROR:No more content.

A sample DDL that demonstrates this behavior is:

CREATE TABLE person (
  id NUMBER(6) NOT NULL,
  first_name VARCHAR2(30) NOT NULL,
  last_name VARCHAR2(30) NOT NULL,
  changed_by NUMBER(6) NOT NULL,
  CONSTRAINT person#PK
    PRIMARY KEY (id),
  CONSTRAINT person#person#FK
    FOREIGN KEY (changed_by)
    REFERENCES person
);

I would need to change the last line to say REFERENCES person (id) for this DDL to be accepted.  This DDL was from a very old Oracle database and I selected 11c/12g as the version.

When trying to make a physical model, I cannot make use of table shortcuts. The option to create a shortcut does not appear when right clicking a table and dragging the table from the navigation pane does nothing either. This issue does not occur when making a logical model, however.

Using Google Chrome on Mac with no extensions enabled. My account is an educational account if that makes a difference.

How can Vertabelo be configured for Postgres to always generate "DROP TABLE IF EXISTS" and "DROP FUNCTION IF EXISTS" when generating a new DROP SQL? The goal is not for migration but regeneration during certain development cycles. There should be a global setting somewhere or in the dialog box. Right now it seems the only solution is to write a brute force shell script to search and replace all occurrences in the drop sql file.