Zdenek Crha
4b54e053df
All checks were successful
continuous-integration/drone/pr Build is passing
Use optional DB open overrides for both input and output database. Duplicating the same override flag for input/output would result in too many, too long flags. It would be too costly for very rare edge-case where converting between same DB engine, just with different flags. Because overrides flags for different engines are disjoint and we are preventing conversion between same input/ouput DB engine, we can have only one set. The override flag will be passed either to input or output, based on engine type it belongs to. It will never be passed to both of them and cause unwelcome surprise to user. |
||
|---|---|---|
| .. | ||
| api | ||
| block | ||
| db | ||
| format-table | ||
| garage | ||
| k2v-client | ||
| model | ||
| rpc | ||
| table | ||
| util | ||
| web | ||