Re: Re: Photo Album Schema
| From: | Bill Zeller | Date: | Fri, 24 Aug 2001 18:29:46 +0000 |
| Subject: | Re: Re: Photo Album Schema | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-11814@lists.php.net to get a copy of this message | ||
Hi,
By saying id.gif, I obviously didn't mean the id of
the user, I meant the unique id of the image.
I assumed the person making this was going to have one
table setup like so:
id (unique id)
owner
name
description
jpg_or_gif, etc
Then a table with authors..
id
name
pass
email
etc
with author.id = picture.owner
I see no downside to doing that and it seems to be a
relatively effecient way to ensure the uniqueness of
all image names.
Best Regards,
Bill Zeller
--- Sheridan Saint-Michel <webmaster@foxjet.com>
wrote:
> I don't know if having multiple users associated
> with a single image is
> at all beneficial, and I can see where it might
> cause all sorts of problems.
>
> For example, you and I both have the same image in
> our album (we are
> both assciated with it in the DB). What happens
> when I change the
> description? Do you change the description field,
> thus changing the
> description on both our pages? Do you now have to
> create another entry
> in your Image table? In effect anytime I change the
> description either both
> of us have to live with my new description or you
> have to do a lot of work
> around code (checking to see if more than one person
> is associated with the
> image, Adding a new entry into image, changing all
> my info to reflect the
> new
> Image_Name) to avoid this.
>
> Therefore, I think for this project, the original DB
> structure works much
> better.
>
> Sheridan Saint-Michel
> Website Administrator
> FoxJet, an ITW Company
> www.foxjet.com
>
> ----- Original Message -----
> From: "grant" <grant@amadensor.com>
> To: "Sheridan Saint-Michel" <webmaster@foxjet.com>
> Cc: "Bill Zeller" <billzeller@yahoo.com>;
> <php-db@lists.php.net>
> Sent: Thursday, August 23, 2001 1:48 PM
> Subject: Re: [PHP-DB] Re: Photo Album Schema
>
>
> > The most useful schema would be to have the name
> of the document be system
> > generated, like i123456789.img and make the
> database as follows:
> >
> > Image
> > Image_Name varchar(50) primary key
> > Original_Name varchar(50)
> > Description text
> >
> > User
> > User_ID int8 primary key
> > Login char(8) uniques index
> > password varchar(50) encrypted
> >
> > relation
> > User_ID
> > Image_Name
> >
> > Now you have duplicate anems OK, multiple users
> associated with any
> > picture. You just rename the file as it comes and
> goes.
>
>
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, e-mail:
> php-db-unsubscribe@lists.php.net
> For additional commands, e-mail:
> php-db-help@lists.php.net
> To contact the list administrators, e-mail:
> php-list-admin@lists.php.net
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/