View Single Post
Old 12-16-2017, 06:29 AM   #12
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Antinoos View Post
As stated in my OP, there's no need for porting the cc.db between different fw versions, but between different devices of the same type (or possibly between a PW3 and KT3), running all the very same fw, and containing an identical library.

And as you can read from my profile, I'm using 5.8.11 and will never ever update to the nasty 5.9.2...
5.9.2 is what I had to test on.
I know you are using 5.8.11, that is why I said for you to check for yourself.

Sorry, but the inventors of SQL standardized on a portable text file based backup and restore.
Not my fault that the format is more portable than your use case requires.

Maybe you could find some proprietary tool that does backup and restore to an obfuscated binary file format (search: MS?, Lab126?) that you can not use a text editor on.
knc1 is offline   Reply With Quote