Finally got the "Model cannot be saved because you've reached table limit (20 tables)." message. I have no problem paying, and would have been more than happy to. Except, I didn't see the little blue message until I had painstakingly crafted around 40 tables. Then, clicking the "Change account plan" button destroys every change I made since I hit the 20 table mark... ouch.

We paid after figuring that out and are still using (and for the most part really liking) vertabelo. That one issue just really stung. You might consider a big modal that stops users in their tracks until they click "I'm OK losing my changes" or something.

When logging in, I am always taken to the last model I've worked on. I think a better experience would be to land on dashboard and allow us to select which model to work with in the current session. Maybe even a radio button option on the dashboard:

Login: - Return to last model or - Return to dashboard

Hello is it possible to import images?

Please advise.

Hi!
You've mentioned ORM Tools in Show features list at http://www.vertabelo.com/pricing/plans
I drastically interested in PHP>Propel feature but can't find it in my free account interface.

When generating SQL it would be nice to be able to select a specific schema only. So only table in that schema will be generated including references from tables in that schema to another schemas

I want to change my login email address to a different e-mail. How do I do this?

It would be nice when using a team account I can share a model with team members by selecting them instead of entering the email addresses.

And for big development and admin teams sharing with groups instead of individual members would be nice to

When adding a reference, a FK is automatically generated. Can you provide an option to disable this behavior?

For example, I will typically create the tables with the keys defined per my own naming convention and then create the references. The current behavior is a new field is automatically added as a FK and has to be manually deleted. My colleagues who are using Vertabelo would like to see the current behavior either removed or an option on the model itself to disable the behavior.