On Tue, 2008-09-30 at 17:31 -0500, [EMAIL PROTECTED] wrote:
> Author: ubernostrum
> Date: 2008-09-30 17:31:06 -0500 (Tue, 30 Sep 2008)
> New Revision: 9106
>
> Modified:
>django/branches/releases/1.0.X/docs/ref/models/querysets.txt
> Log:
> [1.0.X] Apply doc fix from [9105]; refs #9255.
Can
Thanks Graham, I'll check that out.
I was going to file a ticket for this, but it seems streaming isn't
really "supported" anyways, so I had to change the approach.
On Sep 30, 8:19 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Oct 1, 11:06 am, David Cramer <[EMAIL PROTECTED]> wrote:
>
> >
On Oct 1, 11:06 am, David Cramer <[EMAIL PROTECTED]> wrote:
> I'm running into an issue when trying to pass a file-like object to
> HttpResponse and telling it to label it as "application/xml"
>
> def sitemap(request, sitemaps, section):
> page = request.GET.get('p', 1)
> fpath = os.path
On Tue, 2008-09-30 at 03:24 -0700, David Cramer wrote:
> Oh, and it's also selecting the user in that history log query and not
> using it.. at least from the looks of it.
So work out what the actual problems are (or might be) and please file
some tickets. Please don't use the mailing list as a
I'm running into an issue when trying to pass a file-like object to
HttpResponse and telling it to label it as "application/xml"
def sitemap(request, sitemaps, section):
page = request.GET.get('p', 1)
fpath = os.path.join(settings.BASE_PATH + '/', 'cache/sitemap-%s-
%s.xml' % (section, pa
In revisions 9102 and 9103, I committed the changes to django.VERSION
and django.get_version() announced previously[1].
To recap:
The VERSION tuple in trunk is now (1, 1, 0, 'alpha', 0), and
get_version() in trunk now prints "1.1 pre-alpha SVN-9103".
The VERSION tuple in the 1.0.x branch is now
At least part of it seems to be fixed here:
http://code.djangoproject.com/attachment/ticket/9083/getAdminLogRelated.patch
On Sep 30, 5:24 am, David Cramer <[EMAIL PROTECTED]> wrote:
> Oh, and it's also selecting the user in that history log query and not
> using it.. at least from the looks of it
Oh, and it's also selecting the user in that history log query and not
using it.. at least from the looks of it.
On Sep 30, 5:23 am, David Cramer <[EMAIL PROTECTED]> wrote:
> It seems theres some issues, and this may go outside of the scope of
> the admin history log (I didn't dig into the code).
It seems theres some issues, and this may go outside of the scope of
the admin history log (I didn't dig into the code).
1) It looks like it could use a .select_related('content_type') as
it's doing a query for every content type, repeatedly even.
2) It's adding an ORDER BY on the .get()-like qu
I am doing some mildly weird things ..
all are related to the fact that the first iterator (i.e. for data in
myob.data) is _really_ Database heavy, so the entire thing is a very
lazy iterator (with other lazy sub iterators). So in caching the sub
objects (myob) the QuerySet could have been evalu
10 matches
Mail list logo
