`db_flush_mode` should actually be `buffer_flush_mode` because it's used even without dbs

Open
#308 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files, tests, or entry points are mentioned. Start by searching the repository for db_flush_mode and inspect each reference to determine the rename's scope; done means the setting is consistently named buffer_flush_mode, including uses that do not involve databases.

Written by the indexing model from the issue text.

Description

code-enhancement

This issue has no description.

Dominant language
Python
Stars
43
Forks
21
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/flowcept

All issues in ORNL/flowcept

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.