Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
there are a couple of method marked as noexcept, but in reality they may throw an exception.
The first method is Column::getString, since std::string needs to allocate memory, the constructor may fail and throw an exception
The second method is Database::setBusyTimeout, internally if the operation fails an exception is thrown.
I was going to remove the noexcept specifier from the destructors, since they are all noexcept if not stated otherwise, but maybe you preferred to state it explicitely, and since it does not make any difference from the language perspective, I leaved them.