Wednesday, August 8, 2007, 6:22:31 PM, you wrote:
This might be a good place to use the ContentEncoding field to
describe an 'ondisk' encoding.
How do you expect to use this filed?
Something like '(ondisk|inDB),(base64|quoted-printable|...)'?
On Aug 8, 2007, at 5:17 AM, Boris Lytochkin
Lytochkin
Sent: Wednesday, August 08, 2007 9:48 AM
To: Jesse Vincent
Cc: rt-users@lists.bestpractical.com
Subject: Re[4]: [rt-users] Attachments table of RT's Mysql database
Wednesday, August 8, 2007, 6:22:31 PM, you wrote:
This might be a good place to use the ContentEncoding field to
describe
On Aug 8, 2007, at 10:47 AM, Boris Lytochkin wrote:
Wednesday, August 8, 2007, 6:22:31 PM, you wrote:
This might be a good place to use the ContentEncoding field to
describe an 'ondisk' encoding.
How do you expect to use this filed?
Something like
I personally agree with Boris on this. This should be a configuration option
to either store attachments in the database or on the web front end.
So do I.
Moreover, it might be very convenient to store only _unique_ attachments and to
have a counter of 'uniqueness' for each one. After all, RT
