On 12/17/06, Burhan <[EMAIL PROTECTED]> wrote: > A person creates a record for an asset, that has a manufacturer, a > location and an asset type. All these are linked as FK in the model. > Now there is a table that has various properties (Serial Number, Color, > Weight, etc.) -- a master list. From these a person should be able to > pick the appropriate properties that apply to the asset, and enter the > values. So, for a computer they would pick Model Number, Serial Number, > Hard Disk, from the 'master list' and enter corresponding values. These > are stored in a separate table.
def Asset name - CharField manufacturer - ForeignKey location - Foreign Key asset_type - ForeignKey properties - ManyToManyField def Properties name - CharField Properties would include as many or as few as you'd like (Model Number, Serial Number, Hard Disk), and the M2M field would let users as many or as few properties as they wanted to. -- Austin Govella Thinking & Making: IA, UX, and IxD http://thinkingandmaking.com [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
