When generating a single table's SQL also generate the foreign key constraints SQL as separate statements

This would help with contrasting tables. I know you can set the table background color but I also have 100+ tables and setting each individually is a pain.

I would like to see support added for the "char" (single byte) data type.

http://www.postgresql.org/docs/9.0/static/datatype-character.html#DATATYPE-CHARACTER-SPECIAL-TABLE

When Generate Script and Set SCHEMA NAME and TABLESPACE NAME in script ignore the Double Quota, only script for indexes appear double quota in the schema name.

Regards...

If there are multiple fields defined with AUTO_INCREMENT set, MySQL (and maybe other databases) throw an error:
CREATE TABLE test (
#1075 - Incorrect table definition; there can be only one auto column and it must be defined as a key

I noticed Vertabelo has the ability to capture descriptions of the tables and fields within those tables which is great.

I noticed on the SQL export only the table descriptions are included, there is no trace of the descriptions associated with the individual fields. I'm using MS SQL 

Managing a data dictionary is very important to the project I'm working on and I was hoping to do it through this tool but have it ultimately reside in the database.

For example, here is an article on doing it with ERWin,Embarcadero and others: http://www.mssqltips.com/sqlservertip/1619/build-a...

Am I missing the way to go about this through Vertabelo or is that not supported at this time?

when i go to sharing there is no field for adding email.

To print my models it would be nice to export to PDF and select paper size and orientation.
If the model covers multiple pages it would be nice to show the lines on the screen so tables can be moved around and aren't split over 2 pages

If you build a create table script for SQL Server, it fails to run; "ON PRIMARY" is added at the end of all indexes, tables, etc.  - since "PRIMARY" is a reserved word, the script won't work.

Changing the script from "ON PRIMARY" to "ON [PRIMARY]" fixes the issue; could this be done at point of generation?