Your feedback is highly appreciated! Let's make Vertabelo even better.
Nie znaleziono podobnych wątków.
+1
Naprawione
You need to be WAY more obvious when it's time to pay...
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.
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.
+1
Ukończony
Go to dashboard when logging in.
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
Login: - Return to last model or - Return to dashboard
0
Ukończony
Where are the ORM tools?
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.
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.
+5
W trakcie analizy
Generate specific Schema
Raymond Roelands 10 lat temu
•
Ostatnio zmodyfikowane przez Agnieszka Kozubek-Krycuń (Chief Scientist) 10 lat temu •
1
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
0
Z odpowiedzią
Error al crear cuenta
Jose Guevara Ylatoma 10 lat temu
•
Ostatnio zmodyfikowane przez Agnieszka Kozubek-Krycuń (Chief Scientist) 10 lat temu •
1
Cuando estoy creando mi cuenta me sale el siguiente mensaje, cuando boy ingresa, sale que no existe la cuenta.
We already have account with this email. If you created account before and you don't remember
your password please use password reminder.
We already have account with this email. If you created account before and you don't remember
your password please use password reminder.
0
Z odpowiedzią
How do I change the e-mail address for my account?
Charles Hammer 10 lat temu
•
Ostatnio zmodyfikowane przez Rafał Strzaliński (Senior Engineer) 10 lat temu •
2
I want to change my login email address to a different e-mail. How do I do this?
0
Ukończony
what programs can be used to open my database once created?
Patricia Vernon 10 lat temu
•
Ostatnio zmodyfikowane przez Rafał Strzaliński (Senior Engineer) 10 lat temu •
1
+2
Ukończony
Sharing in Team Account
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
And for big development and admin teams sharing with groups instead of individual members would be nice to
Odpowiedź
anonymous
10 lat temu
It's done and on production. Here's where you can find this feature:
+9
Ukończony
Do not auto-create foreign key reference.
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.
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.
Customer support service by UserEcho
