On Sat, Feb 28, 2009 at 11:27 PM, NewSpire wrote:
> First, this restriction is not there in the database. Auto-increment
> fields do not have to be primary keys. Imposing this restriction
> could cause a problem when trying to use legacy tables in a Django
> environment.
Hi Django developers,
This is my first message here. I wish to resurrect Application (default)
settings modules -- a topic that has been discussed here several times. I
bring it up because I believe its current resolution is inadequate (hence it
keeps coming up) and I think I have a new way
>
> Firstly there is no reason for the _factory functions to take a queryset
> argument, the queryset is specific to the formset instance, not the class
> itself. Secondly in no way are 2 arguments more consistant than a single
> queryset argument, because once we add filter someone will request
Hello,
Two weeks ago I reported a security-related bug to
secur...@djangoproject.com, but nobody has replied to my message. I'd
like to discuss the bug publicly, but before I do I want to make sure my
message has actually been received. Can anyone confirm to me that the
address is not simply
On Mon, Mar 2, 2009 at 12:41 PM, PauloS wrote:
>
> >
> > Firstly there is no reason for the _factory functions to take a queryset
> > argument, the queryset is specific to the formset instance, not the class
> > itself. Secondly in no way are 2 arguments more
I received it, but I'm not running any software you mentioned in your list
of vulnerabilities
2009/3/2 Jim Garrison
>
> Hello,
>
> Two weeks ago I reported a security-related bug to
> secur...@djangoproject.com, but nobody has replied to my message. I'd
> like to discuss the
On Sun, Mar 1, 2009 at 8:25 AM, NewSpire wrote:
>
>> 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
Hi Jim --
On Mon, Mar 2, 2009 at 1:04 PM, Jim Garrison wrote:
> Two weeks ago I reported a security-related bug to
> secur...@djangoproject.com, but nobody has replied to my message. I'd
> like to discuss the bug publicly, but before I do I want to make sure my
> message has