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
TryBot-Result: Gopher Robot <>
Run-TryBot: Zvonimir Pavlinovic <>
Reviewed-by: Jonathan Amsterdam <>
3 files changed
tree: 8d104d8ce315b33903f14a0b1acf2e61b2720d80
  1. cmd/
  2. deploy/
  3. devtools/
  4. internal/
  5. terraform/
  6. .dockerignore
  7. .gitignore
  8. all_test.go
  9. checks.bash
  10. config.json.commented
  12. go.mod
  13. go.sum
  15. Makefile
  18. tools.go


This repository contains code that serves

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the time repository is located at Prefix your issue with “x/pkgsite-metrics:” in the subject line, so it is easy to find.