Hi Wei,
On Dec 27, 6:23 am, "wei guangjing" wrote:
> Hi,
>
> I write a patch for using with statement in python 2.5 and up for multi
> database access, example code like this:
>
> # test.py
> from __future__ import with_statement
> from django.contrib.auth.models import User
> from django.db im
Malcolm,
Thanks for the nice reply.
On Sep 11, 2:08 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Why? If your reason is self-documenting code for somebody implementing
> an external backend, we can probably work something out.
Let me be more concrete then. I went to implement a backend.
I'd like to propose that we fix up the abstract BaseDatabaseWrapper
class so that it actually has all the hooks it needs. Right now the
two missing items I'm seeing are the absence of validation and
introspection. There is the expectation that the implementations will
have these and implement th
Malcolm,
Thank you so much for everything you do to help this project. Just
based on changeset dates and time I know that you have put in
countless hours to get this work done. It's much appreciated.
> Indeed! Congrats! Now we need to get brosner to throw this into NFA so
> us branchies can st
This is a small thing but I was encouraged to mention it since we
still have an opportunity to make the change before Queryset Refactor
gets merged. It seems to me that values_list would be more consistent
with things like select_related or order_by. Yeah, it's a small
thing, but what the heck.
> The OP suggests an additive behavior similar to the way filter()
> operates. However, there is also the option of a "last one wins" approach, as
> seen by the order_by() method (on trunk, is it the same in qs-rf?):
Although, you have a point, I have to say that limitation in order_by
bugs me a
Before opening a ticket I thought I would check what the expected
behavior is for generative values(). This is the behavior I'm seeing
on Queryset Refactor branch and to me it seems like it is not the
correct behavior.
>>> from original.foo.models import Category
>>> Category.objects.all()
[, ,
It looks like the cron jobs to update the Django Updates google group
are not working since the server restart. It also appears that the
community updates are not happening as well.
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed
I'm was confirming ticket #2493 (Error resetting app with self-
referencing ForeignKey) this evening and as I began to poke into it it
appears that the fix is what mtredinnick recommended, to use
introspection to get the foreign key relation name when constructing
the alter table drop statement fo
