Constantine Molchanov

I’m talking more about visualizing it. As to analyzing models, we can analyze model instances instead of types which is a lot easier, covers initialization issues, and can be done...

@salva-imm > VARCHAR/CHAR with length support I'm doing this right now in a separate branch. The way I see it, there will be types `StringOfCap[n]` and `PaddedStringOfCap[n]` that will correspond...

> VARCHAR/CHAR with length support Should be addressed in https://github.com/moigagoo/norm/pull/101

> maybe some db specific features?(like HStore/JsonField for postgres) Duplicates #24

Count added in 2.3.0.

No plans so far. Feel free to contribute.

It would be awesome to support it in Norm. I see the package is compatible with Nim stdlib's DbConn type, so it shouldn't be too hard to use.

> Out of curiosity, what would be the point of that ? Probably connecting Norm to an existing table. This can be implemented in a similar manner to `tableName` pragma:...

I'll take a look at this. Shouldn't be too hard. However, custom primary keys have higher priority to me.

Thanks for the kind words, they really mean a lot to me 🙏 Are you suggesting mapping Nim enum type to Postgres enum? How should it be handled in SQLite?