Your feedback is highly appreciated! Let's make Vertabelo even better.
Aucun sujet similaire trouvé.
0
À l'étude
how do you export a list of titles and descriptions for the attributes
Keith Alexis il y a 9 ans
•
mis à jour par Agnieszka Kozubek-Krycuń (Chief Scientist) il y a 9 ans •
1
0
À l'étude
Left/Right panel resize produces unexpected results on secondary displays
Steps to Reproduce:
- Place browser within a display/monitor not set as the main display for windows.
- Attempt to resize the left or right panel using the drag and drop bar.
- Light blue bar appears and drags with with mouse correctly
- When released panel resizes to smallest possible width.
- Light blue bar appears and drags with with mouse correctly
- When released panel resizes to location of blue bar.
- OS: Windows 7
- Browser: Chrome
0
Terminé
Add Support for the PostgreSQL "jsonb" Data Type
It appears "jsonb" data type is not recognized yet, is it possible to add this so my warnings go away.
0
Résolu
column name seems to be invalid
Alejandro Lamothe il y a 9 ans
•
mis à jour par Agnieszka Kozubek-Krycuń (Chief Scientist) il y a 9 ans •
1
Column Name seems to be invalid appears in the Warnings window, it does not say why,
0
À l'étude
Multi column index SQL preview is often incorrect, with missing columns or incorrect order of columns.
Create a table with multiple columns. Create a multi column index that doesn't include the PK. Press the SQL Preview button... maybe it's right, maybe it isn't. Reorder the columns in your index, or add/delete one, and try again. I bet it's not correct now.
0
Terminé
Support "if not exists" clause in sqlite table and index creation.
It would be nice to support the "if not exists" clause for table and index creation when targeting sqlite.
Solution
anonymous
il y a 9 ans
Vertabelo already supports "if not exists" clause in these two statements.
In case of table creation, just expand "Additional properties" section and set "IF NOT EXISTS clause" to "Yes":
You'll then see your this clause in generated SQL:
The same applies to index. Just set the property like this:
and you'll see this in the SQL output:
I hope this helps.
In case of table creation, just expand "Additional properties" section and set "IF NOT EXISTS clause" to "Yes":
You'll then see your this clause in generated SQL:
The same applies to index. Just set the property like this:
and you'll see this in the SQL output:
I hope this helps.
+9
À l'étude
Indicating that the down-scaled table has more columns than are being displayed
Some time ago I have reduced the heights of the largest tables in my database model to minimize its size. That way, I have scaled several tables. Many columns in these tables where hidden. Unfortunately, there are no icons within the down-scaled tables indicating that these tables have more columns than are displayed. In my opinion, this is a fundamental feature to know which tables have additional, hidden content. In all other applications, there are relevant icons (usually in the right bottom corner) indicating that the object has more content inside it. It's very important to have such information available, especially when you're working an a huge database model for a long time and it's very likely that you forget which tables were vertically scaled.
0
Résolu
What is "check expression" (mysql -> table properties -> columns -> details -> check expression)? What should I use?
Henrique Cunha Moreira de Abre il y a 9 ans
•
mis à jour par Rafał Strzaliński (Senior Engineer) il y a 9 ans •
1
What data should I put inside the field "check expression"?
mysql -> table properties -> columns -> details -> check expression
mysql -> table properties -> columns -> details -> check expression
0
Résolu
how to export the DB model into VISIO 2013?
Chaithanya Naik il y a 10 ans
•
mis à jour par Agnieszka Kozubek-Krycuń (Chief Scientist) il y a 10 ans •
1
I have created 2 DB models in vertabelo but now i need to export it to VISIO 2013..
is there a way to export this to VISIO 2013 format?
is there a way to export this to VISIO 2013 format?
+1
Prévu
Update columns in view fails to determin type for CASE expression
Tomasz Traczyk il y a 10 ans
•
mis à jour par Agnieszka Kozubek-Krycuń (Chief Scientist) il y a 10 ans •
1
In my model I have a view using the CASE expression for some column, like this:
SELECT
(...)
CASE WHEN <some condition> THEN b.name
ELSE c.name
END AS name
(...)
When I click the Update columns button, column name is constantly interpreted as int, while both b.name and c.name are varchar (in fact in my case they even refer to the same column of the same table).
I suppose it might be difficult in general to reason about the desired type of case expression, but as for me, silently assuming that it's int, without any warring is a bug.
I've fixed the type manually sometime ago, then today I've added some new columns to my view and then, not remembering about the issue, hit "Update columns", which silently broke my model. I'd rather get an error, that Vertabelo is unable to update columns.
SELECT
(...)
CASE WHEN <some condition> THEN b.name
ELSE c.name
END AS name
(...)
When I click the Update columns button, column name is constantly interpreted as int, while both b.name and c.name are varchar (in fact in my case they even refer to the same column of the same table).
I suppose it might be difficult in general to reason about the desired type of case expression, but as for me, silently assuming that it's int, without any warring is a bug.
I've fixed the type manually sometime ago, then today I've added some new columns to my view and then, not remembering about the issue, hit "Update columns", which silently broke my model. I'd rather get an error, that Vertabelo is unable to update columns.
Service d'assistance aux clients par UserEcho
