Skip to content

feat(config): let the engine control SystemConfig defaults - #14

Open
adsharma wants to merge 1 commit into
mainfrom
engine-controlled-defaults
Open

adsharma wants to merge 1 commit into
mainfrom
engine-controlled-defaults

Conversation

@adsharma

Copy link
Copy Markdown
Contributor

Instead of pinning a copy of every engine default in this binding, both Database constructors (async wrapper and sync) now default all settings to null, and the sync implementation starts from the default-constructed embind SystemConfig (engine defaults) and only assigns explicitly set properties.

Unset settings follow engine-side default changes automatically (e.g. LadybugDB/ladybug#1435 needs no binding change). Explicitly passed values behave exactly as before. Note: this binding never exposed enable_multi_writes/max_db_size, so those were already engine-controlled.

BREAKING CHANGE: Database() settings parameters changed from concrete defaults to null meaning "engine default".

Stop pinning a copy of every engine default in this binding. Both
Database constructors now default all settings to null, and the sync
implementation starts from the embind default-constructed SystemConfig
(engine defaults) and only assigns explicitly set properties.

Unset settings follow engine-side default changes automatically.
Explicitly passed values behave exactly as before.

BREAKING CHANGE: Database() settings parameters changed from concrete
defaults to null meaning "engine default".
@adsharma adsharma changed the title feat!: let the engine control SystemConfig defaults feat(config): let the engine control SystemConfig defaults Oct 27, 2026
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.

1 participant