Re: What DB to use for lots of IMAGE files?

tpcarmen_at_NO_EMAIL_SPAM.SEE_SIGNATURE_FOR_ADDRESS.org (Terry Carmen) wrote:

>In any event, although it's possible to store large files in a
>database, I've had much better performance by storing the image with
>the native underlying filesystem, and only storing the image path and
>filename in the database.
 

>Using one of the keys as part of the path name will allow you to limit
>the number of images in a single directory to an optimum number for
>the filesystem.
 

>For example, under NT, a maximum of a few hundred files per directory
>seems to be optimum, so one system I wrote stores the files as:
 

>\\servername\images\<year>\<month>\<day>\<first 4 digits of image
>ID>\<imageID.TIF>

Although I fully agree with your setup, I was wondering about the implementation of the security. Do you have any ideas if it is possible to limit access based on rights to the database.

As an example assume a table containing usernames and picture names to indicate whether or not a user has access (I know, a lousy setup for maintenance). Now it would be nice if each user could only see the files he/she has been granted access to. And preferably without changing network security for each file (and each time something in the rights table of the database changes).

Any ideas???

Kees Pijnenburg - P.O. Box 84 5374 ZG Schayk The Netherlands

                  kpijnenb_at_xs4all.nl