Non-default Id columns are a source of trouble

Suppose you write:

User
    Id Text

    name Text
    age  Int

This generates t able:

CREATE TABLE user (
    id TEXT PRIMARY KEY,
    name TEXT NOT NULL,
    age INT NOT NULL
);

This will throw runtime errors whenever you try to insert a value with insert - we generate the following code from a insert User { userName = "foo", userAge = 40 } call:

INSERT INTO user (name, age) VALUES ("foo", 40);

But the user table has an id column - that is NOT NULL - with no default!

Approaches:

1. Make insert safe with a class member like the OnlyOneUnique instance. Kind of ugly.
2. Error out on Id Text without defaults while parsing the code. Maybe allow folks to use !force to skip it. Maybe make this an optional thing - a value on PersistSettings.

Start by reproducing the generated INSERT for an entity with Id Text and no default, then trace how that schema and insert are produced. Review the proposed OnlyOneUnique and PersistSettings directions; the issue is done when the behavior for non-default, non-defaulted IDs is decided and the resulting insert or parse-time handling no longer fails at runtime.