Closed Qualenritter closed 4 years ago
I would prefer if we could integrate the version with error checking as unit tests and add a very simple db example to the existing hello world application.
The current example-code-without-error-checking is close to our original design-paper. If the example is too "very simple", then it is less useful for users.
I'd prefer to have one example-file for each backend-type, because the backends are separated in the code, and it is not required or intended, that all of those backends are always linked together to the same executable.
Currently the version with error checking just checks for returned errors, but does not verify, that the written data and the retrieved data matches. To be used within the unit test framework, the error checking should be more strict than this.
Thanks! I have merged this as a db test in 95d42dd4c41843a9f515884807067fe57a942093 (still has to be restructured).
This could be used as a very quick test-case too.
The file "example/db-example.c" was auto-generated (script not included) from "example/db-example-with-error-handling.c", removing anything related to error handling.