I am not very sure if I have any misunderstanding about your
situation, but I am doing a similiar "multi-oneotoone-relation" in my
project. My models are like these:
class Daemon_Event_List(models.Model): ###this is a basic event list,
but only record the event time
event_type = models.PositiveIntegerField()
event_start_time = models.DateTimeField()
event_occur_time = models.DateTimeField()
# following are some types of event, which have onetoone relation to
daemon_evnet.
class Event_General_Levelup(models.Model):
event = models.OneToOneField(Daemon_Event_List)
#....some other fields about this kinds of event.
class Event_Building_Levelup(models.Model):
event = models.OneToOneField(Daemon_Event_List)
#....some other fields about this kinds of event.
This structure runs well for me, up to now. ;)
On 8月22日, 下午12时21分, Catriona <[EMAIL PROTECTED]> wrote:
> Hello
>
> Is it possible to have multiple one-to-one relationships for a single
> class or is there a better way to do it.
>
> What I have is an event which has about 12 fields. Optionally any
> combination of a single weather record, a single event detail record,
> a single survey record and one of four event subclass records may be
> stored against this event. Each of these optional records has between
> 5 and 12 fields each. I could put everything in one big table with
> lots of nullable fields but that is not my preferred option.
>
> Any help would be appreciated.
>
> Thanks
>
> Catriona
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
