Simpler is better. I agree with Bryan, it would complicate the disaster
recovery if files are different locations. + If I ask them to add data
over a set limit to another location and link back to it in the ticket,
I run the risk of them not creating the ticket and/or not uploading the
file.
Uploading a 225mb file over the lan connection to a local web server
should not take long.
Bryan Alsdorf wrote:
> Hi,
>
> German Pizarro wrote:
>> For small sizes, files saved into the database are OK, but for
>> filesbigger than 1MB, wouldn't it be better to save them in the file
>> system (blocked direct access via http, but accesed via php proxy for
>> authentication/authorization)?
>
> This can be a hotly debated topic, I have gone back and forth on it
> many times. The problem I have with storing things on the filesystem
> is you then have an additional set of data you have to back up. I like
> now that everything is in the database and I can backup, replicate,
> etc all in one spot. The con is the database grows considerably.
>
> Best Regards,
