From: Evgeny G. <gaz...@gm...> - 2010-02-02 15:12:17
|
2010/2/2 Andrzej Jan Taramina <an...@ch...> > It used to be that if you did an: > > xmldb:store( $col, $doc, $content ) > > where $content was a string, but an XML string, store() would store the > document as XML, not as a binary document. > > Now it seems that if you do such a store, even though the $content string > is valid XML it now stores the document as a > binary document. > > Looks like Gev checked in a change on the 30th that broke the existing > behaviour. > > I'm not convinced that the prior behaviour was a bug when you were passing > in a string that was in fact XML. But I've > changed my code to pass in a mimetype parameter in our situation to resolve > this. > > Did you setup a mime-type for? if no the content will be stored as binary. Before commit if you will try to store a binary content without mime you will have exception, because content will be stored as xml content. What about XML content not in string but in base64 stream? Think if you store XML content not from element() you can use mime -type "text/xml" as 4th parameter. But what mime must you setup, for many binary docs, for example when you trying unzip somewhere into db? ---- Evgeny |