[sowashieristjaschoninteressant]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Key Changes

Validation

Checklist

• I reviewed the diff and kept it focused on the described change.
• Python changes pass uv run ruff check . and uv run ruff format --check ., or this PR does not change Python.
• Changed behavior is covered by appropriate tests, including a regression test for bug fixes; any limitations are explained under Validation.
• Validation lists the checks or manual flows I ran and their results.
• Relevant documentation is updated, or no documentation change is needed.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:

No release type found in pull request title "Db engine b plus tree". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[sowashieristjaschoninteressant]

uups