Piet Bronders

Results 145 comments of Piet Bronders

Without encryption: ![no_encryption](https://user-images.githubusercontent.com/42484461/155816823-82c73be4-ff08-45e6-8f29-bf8bf8045921.PNG) With encryption: ![yes_encryption](https://user-images.githubusercontent.com/42484461/155816833-7117c6c3-3c28-462f-a682-de01963ccb7f.PNG) So you can clearly see that the first sixteen bytes contain the 'SQLite format 3\000'-header, while the encrypted file contains a randomized salt value.

There should be yes since the C++ wrapper is just executing a query. What are you doing exactly? Could you give me some code that demonstrates this issue?

Hello @MehLoon, The answer to your question depends on if you are working with a **read-only** or with a **read-write** database. Here are the relevant sections from the documentation: >...

Hello @MehLoon, Is there any update on this issue?

Closed #89 due to inactivity

Hello @Cryptoclysm I don't think hiding ALL the errors when setting the verbosity_level is QUIET is a good choice as errors should be shown regarding of the verbosity's level. Another...

Hi @Cryptoclysm, I've been extremely busy lately with stuff happening in the real world so I haven't had the chance yet to ponder about the correct way to implement your...

Hi @Cryptoclysm, This seems to be the culprit: ```C++ const char *char_path = path.alloc_c_string(); ``` This method allocates memory on the heap so it doesn't get cleared when the stack...

Changing the following code: ```C++ const char *char_path = path.alloc_c_string(); ``` to: ```C++ const CharString dummy_path = path.utf8(); const char *char_path = dummy_path.get_data(); ``` Fixes the memory leakage 🥳 Kinda...

Hi @Cryptoclysm, I'll try to release a new build at some point that fixes the issue... (hopefully soonish) Also gotta figure out which approach I will take 🤔