Re: [PyCS-devel] Should we implement that?

[Phillip P. <ph...@my...>]

> Maybe we should switch to store all userinfo data and put that into it's
> own table? Key the username and the userinfo key? So that we don't need
> to implement this for every change Userland might do in the future?

IMHO we shouldn't move *everything* over to a scheme like this, but it does
sound sensible to make a storage space for unrecognised data.  It depends
how it's going to be sent back ... if there's a point where we just send
back a struct containing exactly what we've been given, this sort of storage
makes sense.  If we have to scatter everything through three different
calls, we might as well just add a column to the user table every time
something changes ...

Cheers,
Phil :)