4 ms·
The case I'm considering isn't an application to be used by an analyst, but the analysis of an application used for some other purpose. It's often the case that
by xapata 9y ago
The case I'm considering isn't an application to be used by an analyst, but the analysis of an application used for some other purpose. It's often the case that an application only stores the current state. When there's historical data, it's often snapshots at regular intervals instead of an event log.
Anyway, we're going way down a rabbit hole. All I wanted to say is that if the user, sensor, or application logic emits something weird, sometimes it's correct.
- Demiurge 9y agoAnd all everyone else is saying, constraint to all possible weird values and reject the junk. If you want free form text field, use that. Problem solved. Meanwhile numeric column is numeric only.
- xapata 9y agoI didn't hear it like that from the early comments, but instead encouragement to duplicate more complex logic from the application as database constraints.