Re: Re: PHP Security

Quoting Richard Lynch <ceo@l-i-e.com>: > Actually, internally, it *is* a file, or part of a file, depending on the > database implementation details. (*) Part of a file? Usually. A file? Rarely. And as part of a file, it is likely to be accessed using a more poorly chosen I/O model than if it were in a standalone file. > So you're adding overhead into the storage and retrieve of your content > for some unspecified (so far) benefit. The benefit is clear. If the so-called file is only going to be used by a single PHP-plus-database application and never passed to a normal OS command that operates on files, cool. If it is to be accessed by multiple methods, especially by normal OS-level processes, extracting it from a database into a temporary file so it can be accessed by those commands each time is ridiculous.