Most commonly, you would store all information (including descriptions
in teh database. The amount of data you describe is peanuts for MySQL.
Then, you would probably store a path to an image in the database as
well. You could then store the images on disk outside the database, or
even think about using amazon S3 for that. Takes away your need for
administering a file server :)

Walter

--
Walter Heck, Consultant @ Open Query (http://openquery.com)
Affordable Training and ProActive Support for MySQL & related technologies

Follow our blog at http://openquery.com/blog/
OurDelta: free enhanced builds for MySQL @ http://ourdelta.org

On Wed, May 27, 2009 at 10:50 AM, Pete Wilson <pete...@yahoo.com> wrote:
>
>
> Hi folks --
>
> I am new to MySQL and just laying out what I hope will be just one db that 
> holds all the info for a list of forged or machined metal parts.
>
> Let's say there are 10,000 such parts, each with a unique part number. That 
> part number is the primary index.
>
> Each part has at least one, and maybe several, accompanying photos.
>
> And each part has at least one, and perhaps as many as five, human-language 
> descriptions. These descriptions might be as long as 5,000 characters each.
>
> I believe I have the choice of:
>
> 1. Storing everything -- photos and descriptions included -- in the database; 
> or
>
> 2. Holding some info in the database; and storing photos and descriptions in 
> normal-type disk files apart from the database, with names based on part 
> numbers.
>
> So my questions:
>
> 1. Which scheme is faster and less resource-hogging in reading, updating, 
> adding, and deleting?
>
> 2. I understand there are problems in storing photos in the db. Can one 
> overcome these problems somehow?
>
> Thanks!
>
> -- Pete
>
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql?unsub=li...@olindata.com
>
>



-- 
Walter Heck

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=arch...@jab.org

Reply via email to