When a diagram starts to have too many objects, it becomes impossible to follow the relationship lines. Adding layers would work like this:

A table could belong to one or more user defined layers, and the user can turn on or off the visibility for each layer. For example, I could turn off all layers except for the 'accounting' layer, and I'd have a very clear view of those objects and their relation.

I don't know why no ER diagraming solution has a layering feature but this should be a must for professional diagrams, this could set you miles apart from other solutions.

I'm trying to create a Vertabelo model from an existing Postgres schema. It looks like you can't create a model from a Postgres database connection, so I exported my Postgres using pg_dump to SQL text and tried Vertabelo "Create New Model" "From SQL".

I get an error message: "SQL import failed. Either our parser is not perfect or your SQL syntax is invalid." with no other info.

1) What's the best way to make a Vertabelo model from an existing Postgres database?

2) The SQL import should give a more useful error message. The lack of useful error info means I don't know what I could do to fix it (e.g, play with Postgres pg_dump export options to get SQL that Vertabelo can read.)

Is there a way to show only the Entity, or the Primary Key of the entity, instead of all the attributes for the entity? Alternatively, is there a way to "shrink" selected entitites in order to fit more entities in a subject area?

how can i display the table filed description in the mysql data model doc?

Hi,

Let' say I reversed engineered from an existing DB which got data records. I want to add more columns to 1 table. I can only see create and drop script. If i do this, I will lose the data records. Any way I can retain them?

Regards,

Farouk Yew

I want to add sample data to the table I created to be able to simulate real table relationalship.

I did Data Modeling training from Mindmajix.

I am new to working with Data.

So I have a lot of data based on time.

Data row for every 15 mins. Should I compute the data and store data for every 1 hour, 1 day, 1 month on the database?

if I do would this schema be good.

{
   _id: "joe",
   name: "Joe Bookreader",
   time min: [
                {
                  time: "1",
                  steps: "10"
                },
                {
                  time: "2",
                  steps: "4"
                }
              ]
   time day: [
                {
                  time: "1",
                  steps: "30"
                },
                {
                  time: "2",
                  steps: "30"
                }
              ]

 }

If you have any advice on how I can improve my data modeling knowledge with noSQL, I would be really grateful.

When I test the client against my postgres database it connects but always times out trying the sql test. How can I troubleshoot this ?

When I add a reference it always adds a column like: TableName_pkColumnName. I like it better when the FK reference column has the same name as the parent PK column name, so just: pkColumnName. I added the column in the FK reference manually, and it still adds the other. Then I have to delete the extra column, delete the reference and add a new reference, which is kind of a lot of work for every reference.

Any way around this?

Hello , I am new here.

I had to delete my account and then put it for academic one. I am using for academic purposes. I would like to ask you for help. I downloaded my document. It is in .xml but I cannot upload it. Is there anyway?