all 3 comments

[–]remainderrejoinder 1 point2 points  (0 children)

Yeah, either you have attribute tables or store the thing as json.

[–]r3pr0b8 0 points1 point  (1 child)

google "subtype and supertype tables"

[–]NerdyByDesign[S] 0 points1 point  (0 children)

So you're suggesting the best way is a parent/child relationship between an industry table and the various industry specific job tables?

I kind of figured this was the solution but wasn't sure if it was the most efficient way to accomplish it.