2) I thought the very smple example explained it. Selecting on a
related field which already is present (so naming the select field
something that exists) would cause it to disappear, no errors, no
warnings.
3) This is a pretty major change to Django, and there's nothing on the
page that says "HEY WE JUST CHANGED THE ENTIRE DBAPI ALL YOUR HACKS
WILL BREAK" (I didn't even know QSRF was released until someone
pointed it out to me)
On Apr 29, 10:51 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 29, 2008 at 11:35 AM, David Cramer <[EMAIL PROTECTED]> wrote:
> > 2) Is the issue still present if you do
> > extra(select={'myforeignkeyname': 1}) ?
>
> Is the issue still present where you didn't explain what you were asking
> about?
>
> > 3) Most importantly. Is there a shiny new page in the documentation
> > that I don't see tagged somewhere that explains the new functionality?
> > If so, can we tag it as "Updated" or whatever is appropriate :)
>
> Documentation update worked like any other documentation update from
> any other commit of any other feature(s).
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
