On Thursday 15 March 2012 14:26:41 Charles Duffy wrote:
Restated: "ADD is to REPLACE as STORE is to... what?"
REPLACE, like ADD, expects the content given to be parsed rather than raw. ADDing the same content twice can result in two documents with the same name in the database; I'm presuming that duplicate STORE commands have similar peril attached.
ADD is intentionally implemented that way and applies only to XML documents and this is why there is the REPLACE command. I must admit it is a little bit confusing for new-comers, so we could add a setting which controls the behavior.
What is the appropriate mechanism to use when replacing one version of raw content with another?
As already said the behavior applies only to XML documents, i.e. STORE does not have this "peril". This means, that you can use STORE to replace existing raw files.
Regards, Dimitar