Glenn,<br><br>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.<br><br>Are you doing something different?
<br><br>Shai<br><br><div><span class="gmail_quote">On 9/7/07, <b class="gmail_sendername">Glenn Wybo</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hi,<br><br>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.<br>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.
<br>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.
<br><br><br>thanks,<br><br>Glenn<br>_________________________________________________________________<br>Ontwerp je eigen Space op het net en deel wat je lief is met je vrienden!<br><a href="http://spaces.live.com">http://spaces.live.com