Re: Best MySQL schema for storing image processing jobs?

[Phillip Ward]

The "Table Per ..." Model is almost always a Bad Idea (although, in this case, Partitioning your table by Stage would do pretty much the same thing).
With proper indexing, a single table with a Stage column will do very nicely.

Where you may need other tables, though, is to track each request over time.
Whilst each record knows its current state, it has not idea what happened to it before, how long that previous activity took, etc., etc. For that, you'll need an other table to track each request as it enters or leaves each state. YMMV.

Regards, Phill W.