[Rt-devel] Storing of attachments.
js138 at eng.cam.ac.uk
Tue Oct 26 06:47:41 EDT 2004
On Mon, 25 Oct 2004, Jesse Vincent wrote:
> > What I'm looking for is a way to store these on disc outside of the
> > database itself.
> > Advantages:
> > 1. Database doesn't grow as quickly.
> > 2. Attachments on disc can be purged more simply.
> That could be taken care of with a tool
Are we always this dismissive? :-)
Maybe, but I'd still like a stub attachment to show in the ticket.
Currently if one runs with the default settings -
$RT::TruncateLongAttachments and $RT::DropLongAttachments undefined -
large attachments get silently dropped. (setting DropLongAttachments
causes a log message, but if neither is set the code falls through and
I'd like at least a note in the ticket that this has happened.
Also it's not just a case of purging attachments - some I just don't want
to be in there in the first place - what is the merit of keeping the image
files in there? I can't usefully search them by content.
The other large attachments we get tend to be data that is needed once by
someone. I'd like to make that available without stuffing very large
attachments into my DB. Having it on disc where it can be downloaded and
then manually removed would fit our usage pattern quite neatly.
More information about the Rt-devel