|author||Zvonimir Pavlinovic <email@example.com>||Fri Sep 08 17:17:03 2023 -0700|
|committer||Zvonimir Pavlinovic <firstname.lastname@example.org>||Mon Sep 11 15:58:44 2023 +0000|
internal/bigquery: order columns in SchemaVersion In relational algebra and hence bigquery, the order of columns does not matter. Hence, two schemas with same columns but different ordering in code definition should be regarded as same. SchemaVersion did not account for that before. It does so now. This problem manifested when patching tables in bq: adding a new field to the middle of govulncheck.Result would result in appending that column to schema in bq. The schema equality check would then fail although it should not. Change-Id: I1d47f59d1d8a415e2976ebe699c37a7b2180a8f6 Reviewed-on: https://go-review.googlesource.com/c/pkgsite-metrics/+/526556 TryBot-Result: Gopher Robot <email@example.com> Run-TryBot: Zvonimir Pavlinovic <firstname.lastname@example.org> Reviewed-by: Jonathan Amsterdam <email@example.com>
This repository contains code that serves pkg.go.dev/metrics.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the time repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/pkgsite-metrics:” in the subject line, so it is easy to find.