| ▲ | ambicapter 16 hours ago |
| What's in them? |
|
| ▲ | unclad5968 15 hours ago | parent | next [-] |
| Data from measurement tools. Everything about the tool configuration, time of measurement, operator ID, usually a bunch of electrical data (we make laser diodes) like current, potential, power, and a bunch of emission related data. |
| |
| ▲ | arethuza 7 hours ago | parent [-] | | I think I'd rather work with very wide tables than the entity-attribute-value approach - which seems like a good idea but rapidly becomes a mess... |
|
|
| ▲ | jayanmn 15 hours ago | parent | prev [-] |
| Property1 to 20 or more is an example. There are better ways to do it but I have seen columns for storing ‘anything’ |
| |
| ▲ | Spivak 14 hours ago | parent [-] | | Sounds like a generic form of single table inheritance. I don't honestly see any other way to do it (punting to a JSON field is effectively the same thing) when you have potentially thousands of parts all with their own super specific relevant attributes. I've worked on multiple products that have had a concept of "custom fields" who did it this way too. |
|
