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

  1. Forum: Vertabelo
+1
Under review

Graphical representation of UNIQUE columns

Max 7 years ago • updated by Rafał Strzaliński (Senior Engineer) 7 years ago • 1

Why isn't there a "U" on the right side next to type like there is a graphical representation for private and foreign keys? I know you can set a variable as unique but it doesn't show in the diagram.

0
Answered

Importing New Tables Into Model Erases Existing Content

Matthew Evans 7 years ago • updated by Rafał Strzaliński (Senior Engineer) 7 years ago • 1

I am attempting to import a number of new tables into an existing model, but when I do so (using the SQL Script Option) everything that was in the model previously is erased. Is there way to "merge" in these new tables and not have them simply overwrite what is in place?

0
Fixed

SQL preview is not working for references

Alexander Yermachenko 7 years ago • updated 7 years ago • 4

Actually it was working before new year and now is broken.


Steps to reproduce:

1) Add 2 tables

2) Add reference between then

3) Select reference

4) Press "SQL Preview" button.

Result:

Empty preview (no SQL code except for comments).

0
Not a bug

"Type not supported" error for the default varchar in Postgres. Why?

willie witten 7 years ago • updated 7 years ago • 2

In developing an ER diagram for Postgres, I always get "type not supported" error for the default varchar. If I don't change anything, it warns me about % sign, if I leave the () blank then I get a warning, which is better than an error, but this isn't great.


Am I missing something?


Thanks,

willie

Answer
anonymous 7 years ago

I believe the behavior is correct. Let's go through all the cases you described.


First of all, the default varchar (that is one without lenght) has syntax: "varchar" or "character varying". You can write it this way in "Type" field and you get no error:


Database accepts it without warning:

tests=> CREATE TABLE def_varchar (
tests(>    id int  NOT NULL,
tests(>    code varchar  NOT NULL,
tests(>    CONSTRAINT def_varchar_pk PRIMARY KEY (id)
tests(> );
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "def_varchar_pk" for table "def_varchar"
CREATE TABLE


Then, if you try either "varchar()" or "varchar(%)", both Vertabelo and PostgreSQL will raise an error:


tests=> CREATE TABLE def_varchar (
tests(>    id int  NOT NULL,
tests(>    code varchar()  NOT NULL,
tests(>    CONSTRAINT def_varchar_pk PRIMARY KEY (id)
tests(> );
ERROR:  syntax error at or near ")"
LINE 3:    code varchar()  NOT NULL,
                        ^



tests=> CREATE TABLE def_varchar (
tests(>    id int  NOT NULL,
tests(>    code varchar(%)  NOT NULL,
tests(>    CONSTRAINT def_varchar_pk PRIMARY KEY (id)
tests(> );
ERROR:  syntax error at or near "%"
LINE 3:    code varchar(%)  NOT NULL,
                        ^

Please note that the list of data types is only a helper to choose the most common ones. You can provide any text you want into the "Type" field. Vertabelo either warns you or raises an error if it doesn't recognize the type, but you can ignore it if you like.


Hope this helps.

+4
Completed

Notes sizing and re-sizing

Rebecca Cremona 9 years ago • updated by anonymous 7 years ago • 2
I often use the text notes feature to annotate my tables. It's unfortunate that the notes don't default to a reasonable size, but instead become wider and wider, aiming to fit an entire paragraph on one line. Thanks for letting me re-size, after the fact..... but then, if I go back and edit the text, the notes become hugely wide again, and have to be resized again. Notes should default to a reasonable width, with text-wrapping, and once resized, should keep their specified widths.
+15
Completed

Selective Table SQL generation

Raymond Gigliotti 9 years ago • updated by anonymous 7 years ago • 3
Have the ability to select multiple tables (already done) and then click the SQL button which generates only the tables and their related objects.
0

Calculated Fields

Marko Frntić 7 years ago • 0

Vertabelo is great but it's missing Computed Columns feature, at least in SQL Server projects.

So Calculated Columns are created like this (Inventory), and I really think that implementing this feature for you is not a big trouble. 

CREATE TABLE dbo.Products
(  
    ProductID int IDENTITY (1,1) NOT NULL  
  , QtyAvailable smallint  
  , UnitPrice money  
  , InventoryValue AS QtyAvailable * UnitPrice  
);

Full documentation on https://msdn.microsoft.com/en-us/library/ms188300.aspx

0
Answered

Modify Database

Bhaskar G 7 years ago • updated 7 years ago • 2

Once I generate SQL and create my database, is it possible to generate "modification" sql, which might involve saving old data and re-inserting in new tables?

0
Under review

Your file is not valid with our XSD

hamza özder 7 years ago • updated 7 years ago • 2

I get this error message while I try to add my old xml doc. I made it with vertabelo in 2015

Answer
Adam Mościcki 7 years ago

Hello,


Please send your XML file to our email address: contact@vertabelo.com


Best regards,

Adam


0

If auto-logged out, please make it so logging back it will take me directly back to the project I was working on

Eric Norcross 7 years ago • 0

Currently, if my computer goes to sleep or I'm otherwise auto logged off, I'm required to log back in and navigate back to the project I was working on. I would be great if logging back in would take me directly there (or better yet, don't auto log me off and allow me to just reconnect and pickup where I left off)



Customer support service by UserEcho