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

Does Vertabelo offer database plans or just design services?
Do I need a third-party database service?
or ...
Does Vertabelo offer database plans?
Thanks Anyway,
- Emanuel Messias, R.d.S (Brazil)

NONCLUSTERED PRIMARY KEY
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.

how to use the reverse Reverse engineering to? 14?
is it possible to get an example to SQL Server 14? I'm don't know anything of java

Please:
1. Download reverse engingeering http://www.vertabelo.com/_file/reverse-engineering/reverse-engineering-1_6_12.jar
2. Download jdbc driver https://www.microsoft.com/en-us/download/details.aspx?id=11774 (exe file should install jar somewhere)
3. In the download folder do:
java -cp .:reverse-engineering-1_6_12.jar:sqljdbc4.jar com.vertabelo.reverse.Main -url jdbc:sqlserver://[serverName[\instanceName][:portNumber]][;property=value[;property=value]] -user USERNAME -password PASSWORD -o OUTPUT_FILENAME
I hope this helps.
Best regards,
Adam Mościcki

Support for Postgres array data types
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.

FK tag in "properties" column of auto-generated documentation
Is it possible to add the "FK" in the "properties" column of the fields that are foreign keys in some table, just like it says "PK" for the primary key?

how to prevent Vertabelo to open multiple browser tabs ?
Is there a way to avoid Vertabelo to open multiple browser tabs (each time I open a document/model ) ?

How many columns can be displayed in a table?
We have a fact table in a physical data model. Even though we have over 120 columns in the table, only a few are visible regardless of how we resize it. Is there a limit to how many columns show in the table? Can we modify it?

[Postgres] Migration Script Error - SET DEFAULT now()
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.
Kundesupport af UserEcho