Hello, I am designing a database to hold scientific observations of animals in the field. The database will be used for several different projects. The basic unit for all projects is the observation, and observations across projects will store the same basic information (and use the same logic), but projects may also need to store some additional information. My plan is to have one main observations table/model/controller, and then additional project specific tables. Each project then hasMany observations and each observation belongsTo one project, and in the observation view I will then find the appropriate project specific table and adjust my forms/displays appropriately.
Any thoughts or critiques of this approach? Secondly, I need to store a hierarchical species taxonomy (kingdom, order, genus, etc) in the database and allow users to update it (species classifications are changed frequently). The logic and view for each level is nearly identical, and I would like to avoid creating separate models and controllers for each. The best approach for me would be to dynamically change the table used by a model. My search suggests that this is not possible, but does anyone know for sure? I could also create a new class and inherit from it, but this would still involve creating a separate model and controller file for each level, which is less than ideal. Any suggestions? Thanks --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
