Posted by Michael Fesser on 12/13/06 20:40

..oO(Jerry Stuckle)

>Sure they are. What happens if you accidentally delete an image from a
>directory?

User error. What if you accidentally issue a DELETE FROM query without a
WHERE clause?

>What if you have the images on another server and want to
>restrict access?

Can be done without a database.

>How about keeping thousands
>of images in a single directory? Even Linux slows down when the number
>of images gets big enough.

Depends on the filesystem. But anyway, it would make sense to use some
subdirectories (one for each gallery) instead of just throwing them all
together.

> And how about keeping track of names so you
>don't get duplicates?

The same way as you would do in a database: auto-generated IDs (if
necessary).

>They are all real problems.

But easy to solve.

>> It will _definitely_ take longer, see below.
>
>It doesn't have to.

Calling a script and querying a database will always be slower than just
returning a static file.

>> For every(!) single non-static image you have to call a PHP script,
>> which already slows things down:
>
>So? If you want to protect your images, you'll have to call your PHP
>script anyway. No big deal.

Question is if the images in a gallery have to be protected (the OP
didn't mention that) or not.

Micha

[Back to original message]