I think the most natural fit for this is a database like the google
appengine provides, not a relational one:
Attach a review to an encounter whenever needed, and access it as an
attribute of the encounter
On Aug 19, 11:29 pm, omat <[EMAIL PROTECTED]> wrote:
> Another approach can be to generat
Another approach can be to generate the Review model dynamically as
explained here:
http://code.djangoproject.com/wiki/DynamicModels
This way, the Review model can be generated dynamically based on the
Encounter model: For every field in the model create 3 for the Review.
So, changes to the enco
2 matches
Mail list logo
