we've just written support for a choices=True setting, when we noticed that we don...

we've just written support for a choices=True setting, when we noticed that we don't actually need it. instead of using special column property to enable row.column.id and row.column.value separation, the user is free to implement this behavior himself by simply making the value a dict.
in fact, when using model forms, this new behavior will be in the way, since when used with foreignkeys, we would have to map r.column.id to fk.id and r.column.value to fk, so that r.column.value.id == r.column.id; all that is completely unnecessary.

we're commiting this anyway to log it, but will revert right afterwards