On Sun, Mar 1, 2009 at 2:31 PM, PauloS wrote:
>
> > Perhaps I'm not making myself clear, but it ALREADY take a queryset
> > argument:
>
> Alex, I know this, but last time I checked BaseInlineFormSet does not.
> Same case with *formset_factory helper functions. It's clear why not,
> it's because t
Now for some leg work.
The simple part is to remove the primary key assert in
AutoField.__init__.
The hard part is that django creates tables with multiple sql
statements. One for the table create and then one for each index.
MySQL requires that auto_increment fields must be indexed. Since
dja
> Perhaps I'm not making myself clear, but it ALREADY take a queryset
> argument:
Alex, I know this, but last time I checked BaseInlineFormSet does not.
Same case with *formset_factory helper functions. It's clear why not,
it's because these helper functions are supposed to build the queryset
for
> my records are created in several satellite systems
Ah, that is, the legacy database is involved. It makes the example
even more vivid - having a legacy primary key while still having the
convenience of a non-primary autofield.
I fully agree that we better should NOT add any backend-dependent
> MySQL, if I recall correctly,
> flat-out will not support this at all.
Correct! MySQL definitely does not support multiple auto-increment
fields. However, that is not what I'm talking about. I would just
like the primary key requirement removed from the AutoField. MySQL
definitely does not
On Sun, Mar 1, 2009 at 7:41 AM, Alex Myodov wrote:
>
> Well, according to "If there's some really strong use-case that's been
> overlooked here, it can be brought up in a thread on django-dev", I
> think I need to explain the feature a bit better.
>
> Why we may ever need to have autofields being
Well, according to "If there's some really strong use-case that's been
overlooked here, it can be brought up in a thread on django-dev", I
think I need to explain the feature a bit better.
Why we may ever need to have autofields being non-primary-keys?
To be able to use several autofields in a si
As a person that raised the problem initially, I can only add several
words to the current discussion thread on the issue: kmtracey
mentioned that "as I can find no mention of AutoField on the
referenced IRC page, so I'll just put it back to DDN", so, in fact my
explanation of the use case is pres
