|
|
Posted by Jerry Stuckle on 09/29/07 18:19
Bruno Barros wrote:
> I, for my framework, put:
>
> ID
> USERNAME
> PASSWORD
> EMAIL
>
> That is for the simple login / logout / register data.
> Then, according to the application, there is another user table, which
> holds all the user's information. It is always made from scratch as I
> never know which fields my customer requires or my code needs ;). For
> example, for a social networking site you need about me, musical
> interests, ..., but for a customer account on a shop, you needn't such
> things. The main users table only stores what is essential in ALL
> users. Then I make a relation between them, connecting users by ID.
> The record with ID X on main table belongs to ID X on the other table.
>
> By the way, PHPBB3, MediaWiki and such are not frameworks, they are
> not made to be as broad as possible. They are ONLY made for themselves
> and their specific needs, while a framework needs us to remember that
> it has to work with all websites from top to bottom.
>
> ---
> Bruno Rafael Moreira de Barros
>
> Adobe Photoshop CS2 and CS3
> -
> XML / XSLT
> -
> MySQL / SQLite / TerraDB
> -
> PHP 3, 4, 5 and 6
>
> :: Looking For A Permanent Job ::
> ---
>
That's one way to do it. But it's not necessarily a good database
design. If there is information specific to that user, I include it in
the same table. Among other things, it saves unnecessary joins.
But this doesn't belong in a PHP newsgroup, anyway. It's more
applicable to a database newsgroup.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|