[CR] SQLite Library

[Ady]

Has anyone used Encryption with the SQLite Library in LabVIEW?

If so, I’d love to hear:

• Which one you used (SEE or SQLCipher or other approch)
• Whether replacing the SQLite DLL was enough, or if the VIs needed changes
• Any gotchas around keys, deployment, or performance

Also, what’s the recommended approach if I want to use SEE/SQLCipher/Other with this library?

More specifically, if I want to use encryption together with this SQLite Library, what would be the recommended approach?

• Is it sufficient to replace the SQLite DLL with an encrypted build?
• Are additional API calls (e.g. sqlite3_key) needed in LabVIEW?
• Any advice on best practices for production deployments?

I understand that encryption is not part of standard SQLite, and I’m mainly looking for guidance from anyone who has already gone down this path. 

Thanks in advance for any insights or lessons learned.

[Ady]

1 hour ago, Ady said:

Has anyone used Encryption with the SQLite Library in LabVIEW? 

I found a nice solution Encrypted SQLite - A Gift - NI Community would love to hear your experience if you have used something like this.

Edited April 27 by Ady

[ShaunR]

I used to sell a product called the SQLite API For LabVIEW. It supported encryption. It's no longer available as SQLite removed the hooks and forced most people to use the SEE.

SEE is a different source tree that they give you access to after you have paid for it.
SQLCipher uses a modified source code tree and rewrites the SQLite source - they basically put the hooks back in again.

Whichever way you choose, you will have to compile the binaries yourself and support them. You won't be able to just download the binaries from the SQLite website.

It's been a while, and I haven't looked at the source recently, but I vaguely remember there were only a small number of API calls (maybe 2 or 3) that you needed to use

Edited April 27 by ShaunR

[drjdpowell]

On 4/27/2026 at 9:13 AM, Ady said:

Is it sufficient to replace the SQLite DLL with an encrypted build?

Are additional API calls (e.g. sqlite3_key) needed in LabVIEW?

It's reasonably easy to use SQLCipher.  Just pass in the dll and execute two SQL PRAGMAS, one with your license for SQLCipher and one with the database's key (https://www.zetetic.net/sqlcipher/sqlcipher-api/).  No new calls are needed.

[kurtfinch58]

 

drjdpowell said:

It's reasonably easy to use SQLCipher. Just pass in the dll and execute two SQL PRAGMAS, one with your license for SQLCipher and one with the database's key ( No new calls are needed.

 

The PRAGMA route is nice since it keeps the LabVIEW side unchanged. Deployment still feels like the part where people get surprised, especially keeping the matching SQLCipher DLL with the app.