I have one particular db that has multiple attachments in a document with the same name. The users are copying/pasting these attachments into the document and they do indeed stay distinct. With DAOS it appears that a “duplicate” attachment (does it read the $File name to determine this?) only resides in DAOS as a single attachment. Any way to exclude this db from DAOS operations?
Thanks.
Mike
Subject: Don’t check the application properties for DAOS
Uncheck (or don’t check) the box for “Use Domino Attachment and Object Service”
Subject: DAOS doesn’t just use filename
DAOS does a checksum on the whole file. Even if just one character was different in the file, they wouldn’t be recognised as the same file - even with the same size and filename.
It should be a problem to leave it enabled and you’re likely to get better compression and lower disk I/O as a result of enabling it.
Subject: Correct on both responses!
DAOS participation is a database property, and operates independently of other NSF files’ participation. It is off by default, and there is no requirement that any one NSF be DAOS enabled even if others are.
DAOS calculates a checksum for the attachment contents to determine if it is a duplicate of an existing object in the DAOS repository. In fact, the metadata (filename, datestamp) are not taken into consideration at all for this comparison.