that would generally work on the assumption that many photos can belong to
many albums. possibly a bad thing.
> table 1
> > -userid (primary key)
> > -username
> > -password
> > -album_title
> > -creation_date
>
> table 2
> > -photoid (primary key)
> > -photo (jpg or gif)
> > -date
> > -photo_title
> > -description (limited length)
> > -userid (foreign key)
would give you 1 album contains many photos, each photo relating to one
album only.
Steve
"Tatare" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'd rather do it like this (but I'm not sure it's ok...)
>
> table 1
> > -userid (primary key)
> > -username
> > -password
> > -album_title
> > -creation_date
>
> table 2
> > -photoid (primary key)
> > -photo (jpg or gif)
> > -date
> > -photo_title
> > -description (limited length)
>
> table 3
> > -userid (primary key)
> > -photoid (primary key)
>
> reguards.
> tatare,
> http://www.memoroo.fr.st
> (not already available in english - could anyone help me to translate it
?)
>
> Jeff Oien <[EMAIL PROTECTED]> a écrit dans le message :
> [EMAIL PROTECTED]
> > I want to make a photo album that will have users who sign up
> > to create an album and then have the albums open to the public.
> > I was thinking of doing it like this but I've never done a relational
> > database before so if anyone thinks of anything I should change
> > please let me know. Thanks.
> > Jeff Oien
> >
> > Table1:
> > -username
> > -password
> > -album_title
> > -creation_date
> > -id
> >
> > Table2:
> > -id (from Table1)
> > -photo (jpg or gif)
> > -date
> > -photo_title
> > -description (limited length)
>
>
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
