A lil help with DB design

I have a table to store members. For each member, I have flags like manager, verified, etc. How should I be storing the flags? As individual columns in the same table and using bit datatype or creating a new table called MemberStatus and creating 1 row for each flag?

Thanx in advance.

Premal.One table.|||no flags, no bit data

just more to interprete|||Option 1. Flags, bits.
1 = true, 0 = false. Not much to interpret.|||1 = true, 0 = false, Null = unknown ;)|||1 = true
0 = false
6 = not sure
9 = not applicable
NULL = unknown|||10 = drop dead gorgeous.|||7 = very fluffy.

-PatP|||to properly account for shades of gray, you should use a decimal.

.983 = high degree of truthiness
.015 = minor fib, won't hurt anyone|||"truthiness" heh

somebody is a big fan of TheDailyWTF

:)|||nah, i got it from Colbert. He invented that word.|||1 = true, 0 = false, Null = unknown ;)

Null does not mean unknown, it means the absence of any value, or non existence|||ah, i see, thanks brett

but ontologically speaking, "absence of any value, or non existence" includes unknown

it also includes not applicable, out of range, optional, forgot, maybe, and WTF!|||ah, i see, thanks brett

but ontologically speaking, "absence of any value, or non existence" includes unknown

it also includes not applicable, out of range, optional, forgot, maybe, and WTF!

Ummm no, unkown mean there's a quanity, but who knows.

Null means there's not even the understanding of any quantity

And I like the words you keep throwing out there

But shouldn't it be anti-ontologically

http://www.allwords.com/word-ontologically.html|||Ooh! NULL FIGHT! NULL FIGHT!|||Is that where you throw null pointer exceptions?

Sorry. Couldn't resist.|||Null fights usually turn out to be "Much Ado About Nothing".|||Ooh! NULL FIGHT! NULL FIGHT!

LOL

This message is too short