When I export an PDF, my printout looks so tiny. I need to make the text size larger. But I can't

When adding a table for SQL Server and with a column name of Order, the generated SQL incorrectly adds quotes around the column name:

-- tables-- Table: OrderTest
CREATE TABLE OrderTest (
 "Order" int NOT NULL,
 Value varchar(250) NOT NULL
)
;

The generated SQL should be using brackets:

-- tables-- Table: OrderTest
CREATE TABLE OrderTest (
[Order] int NOT NULL,
 Value varchar(250) NOT NULL
)
;

I haven't tried other key words; if you fix this, I'd suggest testing other key words as well.

Thanks!

I was not able ot use my work email address sam@seed.media to sign up

When I am on the pricing page and click the premium account pay per day link, it just takes me to one of my model's page. I want to pay money but can't!

How can I change the Interclassement...? By default he is to latin1_swedish_ci.. I want it to utf8

I tried to send forgot password request it was sent, and trying to login it said my account is inactive but the email did not sent to my inbox, even not in spam. And there is no button to resend confirmation mail.
Please help

Aafter changing a primary key with an identity from an int to a varchar, I noticed there's no check to see if an identity is valid. This should probably popup as an Error.

Comment generation partially works, but it fails to account for a schema in PostgreSQL code generation.

I've added comments to my tables and columns. The table has a schema specified. However the generated script does not reference the schema. For example:

This is the code that's generated:

COMMENT ON TABLE "employee" IS 'Represents an employee.';

This is the code that SHOULD be generated:

COMMENT ON TABLE "schema"."employee" IS 'Represents an employee.';

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