Thanks for the positive comment! It means a lot to me, for real.
Currently, there's no way to shorten or reuse field definition, and `DateTime`
is considered a special case, so _right now_ , unfortunately, it's `birthDate
{.dbType: "INTEGER", parseIt: it.parseInt().fromUnix().local(), formatIt:
$it.toTime().toUnix().}: DateTime` repeated multiple times in your DB schema.
It's the only place you'll have to have this ugly code repetition though.
However, I've been thinking a lot about adding default parser and formatter for
`DateTime` type. In SQLite, they'd be stored as `INTEGER` and in PostgreSQL as
`TIMESTAMP`. Sounds like reasonable defaults.
DateTime is a common type and I can imagine developers rewriting the same
parsers and formatters over and over. Do you think it's a good idea?
