Stefan Benten 5f6fccc6e8 satellite/satellitedb: makes limits nullable change backwards compatible ... Our current endpoints bail on us, if the column data is null. Thus we need to take the intermediate step and set the default to a fixed value and reset those with the following release. It sets the default column value to our current config values of 50GB for storage and bandwidth and 100 buckets, while still enabling the field to be nullable. All 0 values are migrated to be the default as well to ensure they can keep using their projects, as with the original change, 0 actually means 0. Change-Id: I797be80ce2d2105091599dc1b3fc76f74336b66b		2020-09-23 17:54:42 +02:00
..
templates	satellite/satellitedb/dbx: monitor the database calls	2019-12-18 21:57:36 +00:00
gen.go	all: add missing dots	2020-08-11 17:50:01 +03:00
gen.sh	all: use jackc/pgx in place of lib/pq	2020-07-13 15:54:41 +00:00
satellitedb.dbx	satellite/satellitedb: makes limits nullable change backwards compatible	2020-09-23 17:54:42 +02:00
satellitedb.dbx.go	satellite/satellitedb: makes limits nullable change backwards compatible	2020-09-23 17:54:42 +02:00
satellitedb.dbx.pgx.sql	satellite/satellitedb: makes limits nullable change backwards compatible	2020-09-23 17:54:42 +02:00
satellitedb.dbx.pgxcockroach.sql	satellite/satellitedb: makes limits nullable change backwards compatible	2020-09-23 17:54:42 +02:00