cintanotes best practice
Posted: Sat Dec 13, 2014 2:31 pm
There's probably a ton of best practice scattered over this forum and in the way that people use cintanotes. I'm not thinking of goodies here, and I'm not saying everyone needs to do this.
Here's an example I picked up by accident looking for something else. I like this because it is proactive and is a lot better than my old way of doing absolutely nothing, or sleep walking over the edge of the cliff.
I now have a note in my diary to check data integrity of my database once a week, so I exit cn, and run these commands in a dos window in my cn directory (note that I've downloaded sqlite3.exe into my cn directory):
sqlite3 mycintanotesdatabase.db
pragma integrity_check;
ok (is the normal response)
.exit
exit
(The last two commands are to get out of sqlite3 and then the dos window.)
Now it would be good to know which version of sqlite is embedded in each version of cn as it comes out, so that things can be kept in step. Is there an easy way to find out?
Here's another one that I'll do as part of my weekly routine. I'll export the whole database (all notes, all fields) to xml and then create an empty database and import it back in. This is a useful data integrity check and the import reports any duplicates found, which are discarded e.g skipped duplicates 99. This is also one of the options to get out of jail free if something nasty happens.
Just to finish with an example of a recommendation I've found on the forum but I'd like to find out a bit more about it, so it's work in progress:
viewtopic.php?f=6&t=1630
and this extract...
People who need maximum reliability might also consider
sqlite.pragma.synchronous = FULL
(but it will make CN IO operations slower)
After some more research, I've followed this advice.
I'd like my database settings to focus on data integrity (reducing risk of problems, early spotting that they're there) as I don't need high performance - after all it's just me saving the odd note, doing an occasional bit of tagging, and the odd move between sections plus good response when I search.
Cheers
Here's an example I picked up by accident looking for something else. I like this because it is proactive and is a lot better than my old way of doing absolutely nothing, or sleep walking over the edge of the cliff.
I now have a note in my diary to check data integrity of my database once a week, so I exit cn, and run these commands in a dos window in my cn directory (note that I've downloaded sqlite3.exe into my cn directory):
sqlite3 mycintanotesdatabase.db
pragma integrity_check;
ok (is the normal response)
.exit
exit
(The last two commands are to get out of sqlite3 and then the dos window.)
Now it would be good to know which version of sqlite is embedded in each version of cn as it comes out, so that things can be kept in step. Is there an easy way to find out?
Here's another one that I'll do as part of my weekly routine. I'll export the whole database (all notes, all fields) to xml and then create an empty database and import it back in. This is a useful data integrity check and the import reports any duplicates found, which are discarded e.g skipped duplicates 99. This is also one of the options to get out of jail free if something nasty happens.
Just to finish with an example of a recommendation I've found on the forum but I'd like to find out a bit more about it, so it's work in progress:
viewtopic.php?f=6&t=1630
and this extract...
People who need maximum reliability might also consider
sqlite.pragma.synchronous = FULL
(but it will make CN IO operations slower)
After some more research, I've followed this advice.
I'd like my database settings to focus on data integrity (reducing risk of problems, early spotting that they're there) as I don't need high performance - after all it's just me saving the odd note, doing an occasional bit of tagging, and the odd move between sections plus good response when I search.
Cheers