Teie kommentaarid

This bug is caused by different behavior of new Google Chrome (versions 60+) and should work for older versions. 
We are aware of the problem and we are working to resolve it.

Hello Teri,

I have switched your account.


Hope this helps

Hello,


It sounds like firewall related problem.

Can you please send me a log generated by vertabelo client?
It should be located in:

<vertabelo_client_binary_directory>/log/

directory.


Best regards,

Adam Mościcki


EDIT:

Please attach file here.

Hello,


Please write in the `Type` field keyword `serial`. I have checked it and it works as expected.



Hope this helps.


Hello


We will add new domains in the next release (a matter of weeks). 


Hope this helps,

Adam Mościcki


Hello,


I have switched your account to an academic one.


Best regards,

Adam Mościcki

Hello,


I have checked our system and find out that you accepted the team invitation. Do you still need help?


Best regards,

Adam Mościcki

Hello,


If you have at least one tab (with Vertabelo) open, there shouldn't be any session timeouts.

Also "Remember me" is valid one month-long after login.

Everything should work as you expecting.


Do you any have browser extensions? For example, extension which clears browser cookies.


Best regards,

Adam Mościcki





Hello,


Actually, Vertabelo has something like (not exact) layer you described. It is called subject area https://www.vertabelo.com/documentation/database-model-elements/areas. Only `missing` feature is the possibility of hiding areas.
Hope this helps,

Adam Mościcki


Hello,


It looks like you can't create a model from a Postgres database connection,
1) What's the best way to make a Vertabelo model from an existing Postgres database?

There is a way to do that. We have created a standalone reverse-engineering tool, which connects to the database and produces XML model.

Then that XML can be uploaded to Vertabelo.

Comprehensive instruction: http://www.vertabelo.com/blog/documentation/reverse-engineering


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.)

Yes, there is a room for improvement. I will discuss this with my team.


Hope this helps,

Adam Mościcki