We've actually had this debate on the list a few times.
The bottom line is that the smaller your database is, the faster it's
going to be to seek and retrieve records.
Having stuff in the database that has no particular "searchability"
isn't going to do anything for you but slow you down.
The OS'es filesystem is much more efficient at managing files, and you
should take advantage of that.
This is *especially* true if you're ultimately just serving up links to
images in your HTML.
-Jeromie
>>I have a few property listing sites, and usually use a standard
>>reference to find the properties.
>>
>>
>
>What if you have, oh say 100,000 images? Is it still better to have
>file references and save the images as normal files? What about a
>million images?
>
>
>
>
>
>
>The php_mysql group is dedicated to learn more about the PHP/MySQL web
>database possibilities through group learning.
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
The php_mysql group is dedicated to learn more about the PHP/MySQL web database
possibilities through group learning.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/php_mysql/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
