Should things like Distance be stored with their own table? I don't see that an object for 5 feet would benefit from having an image for that distance, nor that it would make sense to share that value with all other things that are 5 feet.
Perhaps this would make more sense to store as simple jsonb. It would even end up saving some sub-queries if, for example, querying for an extension cord that is 5' long.
On the other hand, reuse would end up saving space and would make classes, tables, & schemas consistent.
Should things like
Distancebe stored with their own table? I don't see that an object for 5 feet would benefit from having an image for that distance, nor that it would make sense to share that value with all other things that are 5 feet.Perhaps this would make more sense to store as simple
jsonb. It would even end up saving some sub-queries if, for example, querying for an extension cord that is 5' long.On the other hand, reuse would end up saving space and would make classes, tables, & schemas consistent.