Attachments without Content-Disposition are now generated and shown in the client. This requires a database upgrade as well as rescanning all messages to generate the previously missing attachments. In addition, this upgrade now stores the attachments' Content-ID in the database. This makes it much easier for the client to associate a particular MIME section in the RFC822 message with an attachment in the database and on disk.
10 lines
441 B
SQL
10 lines
441 B
SQL
--
|
|
-- Database upgrade to repopulate attachments. Bug #713830 revealed that
|
|
-- non-text and non-image files with no Content-Disposition were being dropped.
|
|
-- Also add Content-ID to database so attachments in RCF822 messages can be paired
|
|
-- to extracted attachments on filesystem.
|
|
--
|
|
|
|
ALTER TABLE MessageAttachmentTable ADD COLUMN content_id TEXT DEFAULT NULL;
|
|
ALTER TABLE MessageAttachmentTable ADD COLUMN description TEXT DEFAULT NULL;
|
|
|