[development] table vs tables

Shai Gluskin shai at content2zero.com
Fri Sep 7 14:28:58 UTC 2007


I think that all the standard ways of storing images in Drupal is to store
the file location in the database but to keep the photo itself in the
server's /files directory.

Are you doing something different?


On 9/7/07, Glenn Wybo <glennwybo at hotmail.com> wrote:
> Hi,
> I'm starting a project where I need to make a larger database that I'm
> used to make. I can use a little advise on this project.
> Each record in the database will include 1 to 3 photo and some other
> information, in total aproximately 100k of memory per record. I expect a
> total of maximum 500 records per category (1000 categories). So 500 x 1000 x
> 100K = 50G. It is possible to store all data in one table. This database
> will be used between a larger database and the clients.
> My question is: is one table feasable for this amount of data? Or would it
> be recommended to store the data in different tables. The key factor here is
> speed. If the client wants to see some information (always with at least 1
> photo), the time to get the information from the database to the screen
> should be minimal.
> thanks,
> Glenn
> _________________________________________________________________
> Ontwerp je eigen Space op het net en deel wat je lief is met je vrienden!
> http://spaces.live.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070907/907cdc95/attachment.htm 

More information about the development mailing list