Fix Query Timer Resolution

peterallenwebb commented 4 weeks ago

Problem

Previous revisions limited the precision of query time measurements to whole seconds, which is too coarse.

Solution

Record the measurements at full precision, and limit logged values to three decimal places (i.e. millisecond precision) for readability.

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development, and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX

github-actions[bot] commented 4 weeks ago

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

github-actions[bot] commented 4 weeks ago

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

dbt-labs / dbt-adapters