storj/satellite/accounting
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
..
live all: add missing dots 2020-08-11 17:50:01 +03:00
projectbwcleanup satellite/accounting: fix build - time rounding 2020-08-31 09:37:13 -04:00
reportedrollup satellite/orders: use metabase types as arguments 2020-08-28 15:52:37 +03:00
rollup satellite: fix scoping, formatting 2020-07-16 19:13:14 +03:00
tally satellite/metainfo: replace ScopedPath with metabase.SegmentLocation 2020-09-04 10:06:52 +00:00
billing_test.go satellite/metainfo: use metabase.SegmentKey with metainfo.Service 2020-09-03 15:11:32 +00:00
bucketstats.go satellite/metainfo: use metabase in loop 2020-09-01 10:06:16 +00:00
bucketusage.go all: fix dots 2020-07-16 14:58:28 +00:00
common.go all: add missing dots 2020-08-11 17:50:01 +03:00
db_test.go satellite: make limits be nullable 2020-09-21 19:34:19 +00:00
db.go satellite: make limits be nullable 2020-09-21 19:34:19 +00:00
projectusage_test.go satellite/satellitedb: makes limits nullable change backwards compatible 2020-09-23 17:54:42 +02:00
projectusage.go satellite: make limits be nullable 2020-09-21 19:34:19 +00:00