Ticket Change Details
Not logged in
Overview

Artifact ID: 3f575f30d86f1cf36d30bf72aef26055c8f5ca4a
Ticket: 67936dc2abc317c54e7bed3b07de0fce6c277511
Fossil SCM as a NoSQL database instead of CouchDB
User & Date: anonymous 2011-01-24 17:25:51
Changes

  1. comment changed to:
    Hi all,
    
    Sorry for using this instead of the mailing list, but is at this moment is just an incidental questions and I don't want to subscribe to another mailing list to just ask a question (I'm planning to use fossil for my development, but not yet). I have being wandering around this project for two months because I think it could be useful as a self contained NoSQL backend for a distributed off-line/on-line web site I'm planning, but I see also that CouchDB [http://www.ibm.com/developerworks/web/library/wa-couchdb/index.html|1] is also used in that precise scenario. Most of the time I see the Fossil vs Git comparison that emphasize Fossil as a DVCS, Could you please elaborate about Fossil-SCM vs CouchDB to elaborate about the NoSQL database nature of Fossil, specially in projects where you are working with semistructured data and on/off-line operation.
    
    Thanks
    
    Offray
    
  2. private_contact changed to: "ef710649033d78de2fe3d27e2d5a1292128303df"
  3. severity changed to: "Minor"
  4. status changed to: "Open"
  5. title changed to: "Fossil SCM as a NoSQL database instead of CouchDB"
  6. type changed to: "Code_Defect"