Thanks Richard,

The reason I didn't do it that way is because I want to be able to
look up later for a given QM, and which trip found it, and if it is
dead, which trip killed it. This is important because then, for
example, you could go find someone who was there and talk to them
about it. Do you you envision a way to do this?

Aaron

On Jul 10, 9:51 pm, "Richard Dahl" <[EMAIL PROTECTED]> wrote:
> While I am not much of a spelunker... why not an attribute of the QM that
> displays the status (found, killed, etc..)?
>
> class Trip():
>    blah ...
>    qms = models.ManyToMany(QM)
>
> class QM():
>    blah ...
>    status = models.Charfield(max = 30, choices = (('found', 'found'),
> ('killed', 'killed')))
> hth,
> -richard
>
> On 7/10/08, Aaron <[EMAIL PROTECTED]> wrote:
>
>
>
> > Is it impossible to have two edit_inline s in a model which refer to
> > the same other model? I've been trying to do this, and get a
> > "KeyError"
>
> > The situation is: I'm writing an app to keep track of cave exploration
> > data. I have trip objects and QM objects. QMs are leads in the cave-
> > passages that haven't been tried yet (Question Marks). Trips can find
> > many QMs, and can also "kill" many QMs by investigating them so in my
> > QM model I have "finding_trip" and a "killing_trip" properties
> > a finding trip is required (core) but a killing trip is not required
> > In the admin interface, when people are entering their trips, I want
> > them to be able to add QMs that they've found and that they've
> > "killed"
>
> > Does anyone have suggestions of another way to do this?
>
> > Thanks,
> > Aaron
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to