Doc patch for bug 44595: interface for administrator to delete attachments - Patch by Frédéric Buclin <LpSolit@gmail.com> r=Colin

git-svn-id: svn://10.0.0.236/trunk@219962 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
lpsolit%gmail.com
2007-02-11 21:14:53 +00:00
parent 35e094b0de
commit a469db9069

View File

@@ -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>