> But storing them in the DB invariably ends up with too many issues > involving DB storage size and query buffer size, compounded by data > escaping/security issues. This on the other hand... I'm a newbie, whatever your saying, BUT and it is a big one; The data has to be escaped anyway, the binary object has to be checked for security breaches with or without the database, so this is reason is by all means wrongly put.
Depends. Use a prepared statement and mysqli for example, and there is no escaping. You should still do a virus scan first, however. Doesn't matter how you store things.
As a newbie, is storing an image in a dB a "good" thing or a "bad" thing?
I tend to go with "depends". We actually store files in a DB in development, as those machines are separate from the grid. Since some are windows, linux, and MacOS, it is far easier to store in a DB than have different code for each development machine depending on their filesystem. Otherwise, in production, neither way really works, so there is the hybrid way I alluded to before. If you are on a hosted server, you may have different filesystem and database limits for storage. That could make the decision for you. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
