Conversation
|
Caution There are some errors in your PipelineRun template.
|
|
Images are ready for the commit at 0e05770. To use with deploy scripts, first |
|
@janisz: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #15855 +/- ##
=======================================
Coverage 48.80% 48.80%
=======================================
Files 2589 2589
Lines 190567 190567
=======================================
Hits 93014 93014
+ Misses 90245 90244 -1
- Partials 7308 7309 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
RTann
left a comment
There was a problem hiding this comment.
Do we need to worry about any backwards compatibility with old numeric types previously stored in the DB?
|
What are "old numeric types"? |
Perhaps I'm just unfamiliar with how the data is stored in the DB. I figured we were storing numeric types in the DB as |
Description
pgx/v5 comes with pgtype so there is no need to use legacy version.