Skip to content

Allow value-level encryption to be controlled by a compiler define - #255

Open
matbech wants to merge 1 commit into
utelle:mainfrom
matbech:patch-3
Open

Allow value-level encryption to be controlled by a compiler define#255
matbech wants to merge 1 commit into
utelle:mainfrom
matbech:patch-3

Conversation

@matbech

@matbech matbech commented Sep 3, 2026

Copy link
Copy Markdown

Description

Allow value-level encryption to be controlled by a compiler define. Preserve enabled default unless SQLITE3MC_ENABLE_VLE is supplied by the build.

Type of Change

Please select the type of change:

  • Refactor (no behavior change)

Problem / Motivation

For Refactors:
Allow value-level encryption to be controlled by a compiler define.

Checklist

  • I have independently verified the issue
  • I am not submitting unverified or speculative changes
  • I understand that AI-assisted changes must be reviewed by a human before submission

Allow value-level encryption to be controlled by a compiler define. Preserve enabled default unless SQLITE3MC_ENABLE_VLE is supplied
by the build.
@utelle

utelle commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Allow value-level encryption to be controlled by a compiler define. Preserve enabled default unless SQLITE3MC_ENABLE_VLE is supplied by the build.

Actually, the unconditional #define SQLITE3MC_ENABLE_VLE 1 remained there accidentally. I simply forgot to remove it after my first experiments with the new feature. The idea was to only enable the VLE feature if it is explicitly requested.

So, it boils down to the question whether the VLE feature should be enabled by default or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants