[development] User Status

[Earnie Boyd]

Quoting Larry Garfield <larry at garfieldtech.com>:

>
> On Mon, 5 May 2008 15:53:22 -0500 (CDT), David Timothy Strauss 
> <david at fourkitchens.com> wrote:
>
>> You're misunderstanding Knuth if you think we should care about storage
>> space or performance on non-MySQL databases. Optimizing for MySQL is not
>> premature optimization.
>
> Since we haven't even decided what data we want to store, talking 
> about the database field type at all is premature.  If we need a 
> boolean field in the database, let's add a schema field type for it 
> and let each database define its own equivalent.  As long as we can 
> read/write to it with 1/0 for true/false, the exact details of the 
> field are irrelevant.
>
> The more important question is what metadata fields do we want on the 
> user object/user table?  Off the cuff I can think of:
>
> - created time
> - last access time (0 means never logged in)
> - last edit time (by anyone)
> - is_blocked (boolean, sadly this is the inverse of the current 
> status column)
> - What else?
>

How about a suspend column which gives a count down timer in days for 
how long the user is blocked?  Cron would handle the count down and 
when going from 1 to 0 would set is_blocked to FALSE.

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/