If you don't want to tackle BLOBS, simply split the images into several directories.
For example, use the least significant digit of the productID or imageID as a
subdirectory name.
At 11:16 PM 12/14/00 -0700, Dick Applebaum wrote:
>At 12:25 AM -0500 12/15/00, Dave Watts wrote:
>> > ... I am told there is a 500 file per directory limit on NT ...
>>
>>This isn't true. I've seen directories with more than 50,000 files on NT.
>>With NT or even with Solaris, though, this can cause performance problems.
>
>Sorry to pass on untrue rumors!
>
>Is there a practical limit, though?
>
>Does this (a 50,000 entry directory) cause problems with things like
>doing a directory listing with an FTP program? Or, Adding, deleting
>retrieving an individual file from FTP or CFFILE?
>
>When, if ever, does it make more sense to store the images as blobs
>in a db... probably in a separate child table (where it would only be
>retrieved when needed), e.g.:
>
> ImageId Integer Identity Primary Key.
> ProductID Integer References Product,
> BinaryImage Image
>
>A db would certainly be a lot easier to manage from a programmer's
>point of view.
>
>Anyone with some real-world experience?
>
>TIA
>
>Dick
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists