Login change

Turns out my xmas code depends heavily upon a false assumption.. I
thought when you logged-in, that your row would be copied into your
session.. THIS WAS NOT SO.. irritating.

It is now so. We already retrieve it, so why not use it? Due to the
schema changes and the xmas stuff depending on this, I had to implement
it now anyway. But the basic idea, is that instead of repeatedly hitting
the database for things unique to the logged-in-user, why not simply
store them in the session.. As is done with other
unique-to-the-logged-in-user variables. 

Done.

The comment describes the potential should we wish to modify the way
this works in future.

the ASSOC change is simply a readability convenience, otherwise the
session gets all the numerically indexed values as duplicates of the
normally associatively indexed values. So saving space in the session..