Yeah, but it seems like there would be some kind of "object" to link to a user, like a "user details" object or something that includes their address, graduation date, etc.
Of course, I guess I may just be thinking too much object oriented and expecting the system to behave that way.
Well, you could do that, and create an object relation. But if all users should have that data, and the data shouldn't be the same for any two users, wouldn't it make more sense to have it as part of the user?
Thanks, I guess you are right. However, how can I enforce certain rules and such on attributes of an object? Like I spoke earlier, I'd like to let people choose if they ant their address publicly visible or not. Also, I will need to group people by graduation year as well so that people can view them.