Would it be possible to add a foreign key to the 'facebook_status' table instead of having duplicates in the 'facebook_status_tags' table?

In my situation, I only have a limited number of tags (around 20), but I'm expecting 10,000's of statuses, each using one or more of those 20 tags.

Comments

2c’s picture

I guess what I'm asking doesn't as make sense as I originally thought, as you'll need the same number of rows in a lookup table and then have to do a join.

icecreamyou’s picture

Status: Active » Closed (works as designed)

FBSST relies on FBSS, not the other way around, so the facebook_status table can't have anything tag-related. It wouldn't be any faster though.

Seems like a micro-optimization to me anyway. If performance is going to be a big problem for you, you'll do much better by focusing on caching solutions (nearly eliminating queries altogether) rather than query optimizations.