I guess my next question would be: can you somehow consolidate all of
the various jobs into a single 'Job' model?  In otherwords, is there
anything so unique about each job that you couldn't represent each job
with the same model?  If this is the case, you could simply give Person
a job_id, and things would work out nicely.

Looking at the 'Judge' model you posted, it seems simple enough that it
could be represented by a single Job model -- I don't know if this is
totally accurate though, since you have no doubt omited code to save
space. 

Google ate my original response :(


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to