tree f6fd4433c6648efdce3d958e8ef0c41346d6eb1c
parent a781a3ad0c626fc0a7aff0ce33b1ef0830ee2259
author shollyman <shollyman@google.com> 1605824283 -0800
committer GitHub <noreply@github.com> 1605824283 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJftu8bCRBK7hj4Ov3rIwAAdHIIAJ1AtdcZQ+AayNBhdC2FP+gQ
 v/nxnDSYGWZVwocySBObgGZH8PuF6v++pwCxxdxwDMrmytpLZ7OflzuZyjnF8j52
 ds4MbZleG10MjRKGXr1d2yWmkobkPXUBEOszm5qkmNk397MmbrWIxO7jUOStlKN3
 gdnn66DY04qw2VOJ/1keutzIwmOYu2lWCTbcaLMVyXYIKcpT4vBXQbVn2piTOejn
 Ma3UxP16d9n0H3uK3UhghySRaThHNKADKDQ94FqDKdFfMkFXQRQ6BNtlETWqYWQD
 ILtqJfpVTgMmwS0dIusOUkOpv+i0mgCNFzY1FX+txkcXE+lKoMDuunC53jI4IZg=
 =bY0/
 -----END PGP SIGNATURE-----
 

feat(bigquery): add support for bignumeric (#2779)

feat(bigquery): add support for bignumeric

This PR adds basic support for the BIGNUMERIC type in BigQuery.

This library has several cases where it tries to infer the appropriate BigQuery type from a native Go type. For big.Rat types, we continue the existing behavior of mapping them to NUMERIC, as the big.Rat doesn't
provide a general way of indicating desired precision or scale to determine whether BIGNUMERIC is a more
appropriate mapping.