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

0
Answered

Vertabelo: Reverse Engineering - Generated XML - Schema property for each table entry

laxmi P 9 years ago updated by anonymous 8 years ago 5
What options/commands do i need to specify so that Vertabelo: Reverse Engineering - generated xml file includes an Schema property for each table entry:

As an example:


<Table>
<Properties>
<Property>
<Name>Schema</Name>
<Value>Public</Value>
<Property>
</Properties>
</Table>
0
Under review

For Postgresql, when generating script with quoted identifiers, also quote column name(s)

Richard Beauchamp 8 years ago updated by Rafał Strzaliński (Senior Engineer) 8 years ago 1

For example, here is the Vertabelo output: CREATE INDEX "Channel_TeamId_idx" on "Channel" (TeamId ASC);


TeamId should be quoted too.

0
Completed

In DB edit mode, enable the left and right panels to be collapsed

Richard Beauchamp 8 years ago updated by Rafał Strzaliński (Senior Engineer) 8 years ago 1

Those panels take up a lot of space and when modeling on a laptop (small screen) they are in the way when trying to view/modify the model. Thanks!

+2

Extend data model versions search capability

Jeanette Bromage 8 years ago 0

Hi,

A 'nice to have' would be the ability to filter data models versions on tag ( as in if a version has been tagged, display it ) as well as manual / autosaved. I'm having real problems manually saving versions, as the save button is mostly greyed out, but I can create tag names no problem.

+1
Declined

How do I represent inheritance for postgresql?

Dane Falkner 9 years ago updated by Nat Colley 8 years ago 3
I am trying to create a model that relies upon inheritance, but I can't see how to diagram that in Vertabelo. Does it support this feature?
0
Answered

is it possible to extract all data model errors into a single document?

Jeanette Bromage 8 years ago updated 8 years ago 2

is it possible to extract all data model errors into a single document?

0

couldn't create model from sql due to parsing issue, even script generated from vertabelo model is failing.

Aneesh K 9 years ago updated by Adam Mościcki 8 years ago 7
I am trying to create new model from SQL file , but its keep failing due to parsing issue. Even failing basic script or for script generated by Vertabelo from other model.
Answer
Adam Mościcki 8 years ago

Hello,

To make it work, please comment out/remove lines at the end of the sql file like:

'ALTER TABLE xxx MODIFY yyy int(11) NOT NULL AUTO_INCREMENT;'

I have removed those lines from your sql and it worked.
Our sql2vertabelo tool has trouble in parsing such statetments.


Also I have shared to you a model which i got. Feel free to unshare me.

0
Completed

Public view link

boo2 8 years ago updated by Adam Mościcki 8 years ago 1

With public (no vertabelo account) access.

Like with our Axure model https links we incorporate in our online documentation. We need link and not an image to reflect changes in the model automatically

Answer
Adam Mościcki 8 years ago

Hello


We provide a way to embed model on a website. An article which explain how to do it: https://www.vertabelo.com/blog/vertabelo-news/how-to-embed-your-database-model-into-a-website Is this what you need? If not please tell what is missing.



0
Answered

cannot generate pdf file

Vaughan Leong 8 years ago updated by anonymous 8 years ago 2

My model can not generate pdf and html format, I try to set the model use two page only but it still cannot generate pdf and html format, But the MS Word format is OK.

Answer
anonymous 8 years ago

The issue was fixed, please check that you're now able to generate documentation in any supported format.

0
Answered

MySQL generated SQL not importing - parse error on quotes

Eric Norton 8 years ago updated by Rafał Strzaliński (Senior Engineer) 8 years ago 6

I'm trying to import sql generated from vertabelo and I'm getting parse errors on any columns that have been put into double quotations. This has changed because the generated files did not do this before. My model is set to Mysql 5.5 and I'm definitely importing into mysql 5.5.


Any one know what the deal is with this?