This is a good point. Well, we could update CouchDB when footnote while you're not using it.
Or the other way around: we use for normal operations CouchDb and on exit we update the SQL. At startup (when speed is required) we use SQL, during the utilization we use CouchDB since I think adding a new note isn't such a big operation to require a super fast db
This is a good point. Well, we could update CouchDB when footnote while you're not using it.
Or the other way around: we use for normal operations CouchDb and on exit we update the SQL. At startup (when speed is required) we use SQL, during the utilization we use CouchDB since I think adding a new note isn't such a big operation to require a super fast db