Short answer: I don't know. It probably isn't straightforward, but it's doable in principle.
Longer answer: Django hasn't been designed with this case in
mind. It's possible it's not the appropriate tool for the job (but
again it might be, I don't know). In my experience you should
avoid doing such things—it's likely to lead to an unmanageable
code mess. Keep it simple. Consider working without a relational
database.
Regards,
Antonis
Antonis Christofides +30-6979924665 (mobile)
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMCU6Coop%3DVU67%2B1Ui%2BswvA2xijUYcre%2B%3D-Z_CzLnf-1pRRXUw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5F1D5ACB-C5D8-460A-B471-D4B537A010F6%40indx.co.uk.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a02e1d2a-b640-4b5e-ba65-bebcba8de66an%40googlegroups.com.