Skip trying to insert generated fields

[mikestefanello]

Describe the bug
Some of my PG tables have generated fields. Trying to insert records for those models will fail, even if you omit the field because the query will still try to insert nil rather than nothing at all.

To Reproduce
Steps to reproduce the behavior:

1. Generate a model for a table in PG that has a generated field
2. Try to insert a model record for that table
3. The insert will fail, ie pq: cannot insert into column "the_generated_field_name"

Expected behavior
Insert/update queries should automatically exclude any generated fields.

[AlekSi]

Some background on why nil/NULL is being added to the query: #146 (comment)

See also #100.