well, as far as I have seen, EnumCols are VarChars on the DB side (at least
this is true for Postgres).
Doesn't this mean a big waste of discspace? Imagine having millions of rows
Or does anyone know if Postgres is optimized at this point, so that is
saves every possibility (string to be precise)
just one time with references to the real values in the rows?
Even if I do use an EnumCol (or something dericed from it) I want to use
the values True, False and None on Python side,
which means the validator/converter has to work (otherwise I would get
strings). But I don't see why the posted converter did not work.
> Try EnumCol.