Closed pveeckhout closed 3 months ago
We had UNKNOWN as our standing for this enum. our database is currently loaded with UNKNOWN's. Just need to fix our enum, and database to account for these changes. We'll have to run a db update to convert all UNKOWN's to null.
I dont think this is unreasonable. it'd be weird to keep a stand-in for null, as we will have many null fields across our database and we should handle them the same.
These changes are for exploration module, not for trade. These changes have not impact on the trade, as trade will try to request this data. and is completely agnostic of how exploration stores this data
fixes #159