Create Attachments on the local filesystem

David Miller justdave at
Wed Oct 22 18:21:36 UTC 2003

On 10/22/2003 10:41 AM -0700, Myk Melez wrote:

> Joel Peshkin wrote:
>> Implementing this is a completely seperate matter.  Perhaps the right
>> thing to do is to ....
>> a) add a mechanism to permit large attachments to span many database
>> records,
>> b) permit a retention policy to be used for large attachments (e.g.
>> Delete if obsolete > 6 months and size > 10MB and undownloaded > 6
>> months and bug unchanged > 6 months)
> Another option is to abstract out attachment storage to an interface
> that handles access to attachment data with implementations for database
> and filesystem storage.  All implementations should be able to store and
> retrieve attachment data.  Anything else (f.e. searching) would be optional.

Another benefit of having the data in the database is if you have multiple
Bugzilla web servers accessing the same database.  Only way around that if
the attachments are in the filesystem is an NFS mount, which is a little

There seems to be a lot of benefits to both methods, so maybe we need some
kind of local configuration option and allow either.  (Or maybe have a flag
on the attachment record and allow both on a per-attachment basis?)
Dave Miller      Project Leader, Bugzilla Bug Tracking System   

More information about the developers mailing list