I do that since years with tables not having a primary key without
problems, but I am only using django orm on those to select data.
Am 28.04.2015 17:35, schrieb Ben L:
It is true that the table doesn't have a primary key.
1, I might be able to talk to the DBA to add a primary key in here and
consensus on the
options that have already been proposed in the "1.9 release planning
<https://groups.google.com/d/topic/django-developers/MTvOPDNQXLI/discussion>"
thread. If you have a different idea, please propose it there.
On Sunday, April 26, 2015 at 6:53:14 AM UTC-4, Thorst
I like the idea of an survey, but find the release question with only 3
options quite limited, how about to allow there to put own numbers
instead of giving fixed answers or at least an other field?
Am 25.04.2015 14:29, schrieb Tim Graham:
Aymeric and I put together a draft:
Am 04.04.2015 14:30, schrieb Tim Graham:
Now that Django 1.8 is released, I wanted to bump this thread for
discussion so we can hopefully ratify this schedule or modify it based
on feedback. In particular, I heard a concern that a six month release
schedule may be too often for the community.
Am 09.08.2014 21:21, schrieb Aymeric Augustin:
I tried to support both Trac auth and GitHub auth but I couldn't make it work.
The argument that "I use GitHub but maybe someone else doesn't want to" came up
a few times in this discussion. It seems to me that it's a theoretical concern about an
