I like the idea of simplifying data models and not repeating functionality when possible. So, no reason a TODO couldn't be a post. I figure it's a bit of text, media, hashtags, at-tags, comment tree like everything else
The only difference I can see is that posts can have a topic like "Finance"
To avoid joins/for perf reasons, maybe just use a discriminator column and have a generic posts table with "type" being the discriminator (values "post" "todo" where "post" rows have the topic ID/name filled in and whatever else makes them unique; all other columns could be shared)
I like the idea of simplifying data models and not repeating functionality when possible. So, no reason a TODO couldn't be a post. I figure it's a bit of text, media, hashtags, at-tags, comment tree like everything else
The only difference I can see is that posts can have a topic like "Finance"
To avoid joins/for perf reasons, maybe just use a discriminator column and have a generic posts table with "type" being the discriminator (values "post" "todo" where "post" rows have the topic ID/name filled in and whatever else makes them unique; all other columns could be shared)