'Schema Design for last updated timestamp with data
I'm messing with a project that currently only has one table really which I think is starting to get quite a few columns. Currently the column is something like: stat_last_update stat_data, stat2_last_update stat2_data. That table already has to many columns for my liking and is growing as the project starts tracking more stuff.
Some of these fields are regularly updated and some of them less so. I was thinking about alternate schema designs that would make the growth of the project better. This is a multi user application so we have been staying away from creating lots of rows and just adding columns.
Would splitting each stat we are tracking into it's own table then having a last_updated table be better? It feels like I'm just forgetting a smart way to do this kind of data.
It just feels like this strategy of adding in columns is going to backfire or at least make updates and maintenance harder in the future as we continue to monitor different things with our app. We would like to keep with our relational database as some stuff in our app benefits from that. This last_update + data stuff is what is throwing me off.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|