mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-11 10:08:41 +00:00
Doc patch for bug 44595: interface for administrator to delete attachments - Patch by Fr��d��ric Buclin <LpSolit@gmail.com> r=Colin
This commit is contained in:
parent
5e117a5fe6
commit
8f1a55ca76
@ -848,12 +848,16 @@
|
||||
|
||||
<para>
|
||||
If you have a really large attachment, something that does not need to
|
||||
be recorded forever (as most attachments are), you can mark your
|
||||
attachment as a <quote>Big File</quote>, assuming the administrator of the
|
||||
installation has enabled this feature. Big Files are stored directly on
|
||||
disk instead of in the database, and can be deleted when it is no longer
|
||||
needed. The maximum size of a <quote>Big File</quote> is normally larger
|
||||
than the maximum size of a regular attachment.
|
||||
be recorded forever (as most attachments are), or something that is too
|
||||
big for your database, you can mark your attachment as a
|
||||
<quote>Big File</quote>, assuming the administrator of the installation
|
||||
has enabled this feature. Big Files are stored directly on disk instead
|
||||
of in the database. The maximum size of a <quote>Big File</quote> is
|
||||
normally larger than the maximum size of a regular attachment. Independently
|
||||
of the storage system used, an administrator can delete these attachments
|
||||
at any time. Nevertheless, if these files are stored in the database, the
|
||||
<quote>allow_attachment_deletion</quote> parameter (which is turned off
|
||||
by default) must be enabled in order to delete them.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
Loading…
x
Reference in New Issue
Block a user