If you can convert it to useful JSON, then I don't see a problem (though I've no idea if this is possible).
Previous revisions of documents are removed during database compaction, you shouldn't think of it as a versioning system for your data. B. 2011/11/8 Маркевич Александр <[email protected]>: > Because after conversions we can have many document fields and properties, > wich can save in CouchDB with history of revisions. And if I want to save > doc from DB - I can accessed to any previous revision of the doc. > > 2011/11/8 Alexander Shorin <[email protected]> > >> 2011/11/8 Маркевич Александр <[email protected]>: >> > Hi CouchDB Team! >> > >> > Can I store *.odt/*.ods files into Couch base? Because it have XML-based >> > format and stability specification (maybe in the future ;). >> > >> > If I can't store ODT on this evolution stage of CouchDB - I want to write >> > or adapt any encoder XML->JSON->CouchDB? >> > >> > What are think about it? >> > >> > P.S. Sorry of my English. >> > -- >> > Best regards Alexander Markevych. >> > >> >> Hi Alexander, >> >> Why not just store them (*.odt files) as document attachments without >> any format conversions? >> >> -- >> ,,,^..^,,, >> > > > > -- > С уважением Александр. >
