[thelist] Where to Store Username and Password in SQL Tables

> It seems really easy to just store the Username and Password in each
> table accordingly.  Like this...
>
> But are there any pitfalls to this approach?

pitfalls?  not really, it's just messier than it needs to be

i mean, think of the logon password verification logic

more twice as much code

yeah, i know, cut & paste makes that sort of thing easy

still, i prefer the simple approach


> Should I create a Users table?

ayup

and store a value in a column called Admin to differentiate between the two
types of user

if your admins don't have to have their address recorded, make sure you
allow those fields to go null


rudy