On Fri, 2007-11-23 at 03:39 -0800, Patryk Zawadzki wrote:
> On 20 Lis, 16:15, "Michal Salaban" <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > We have created a patch which allows customizing the order of Fields in
> > Forms.http://code.djangoproject.com/ticket/5986
> >
> > The initial idea (with
Hello dear Django developers!
Can GenericRelation be used for the following lookup example?
Here subscription is .GenericRelation field name (see model
definitions below).
user_numbers =
LocalNumber.objects.filter(subscription__account=user_account)
I bet it WORKED! But today I noticed this cod
On Nov 29, 12:29 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Drop them in a ticket and I'll commit them.
http://code.djangoproject.com/ticket/6049
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django devel
On Wed, 2007-11-28 at 15:06 -0800, SmileyChris wrote:
> On Nov 29, 9:28 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
> > I've fixed it, after a fashion, in r6721.
>
> Why no tests?
Drop them in a ticket and I'll commit them.
Malcolm
--~--~-~--~~~---~--~---
On Nov 29, 9:28 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I've fixed it, after a fashion, in r6721.
Why no tests?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
On Wed, 2007-11-28 at 13:04 -0800, David Cramer wrote:
> Anything you can think of off hand that's going to hurt by just
> changing it to INNER JOIN right now if we dont use the isnull support.
I think you'll be safe. The only difference is that certain rows won't
appear when the right-hand side
Anything you can think of off hand that's going to hurt by just
changing it to INNER JOIN right now if we dont use the isnull support.
I'm also wondering if it may cause many rows to return (i can't
remember how left joins work, as I don't use them much) vs a single
row, but we use it with GROUP
On Thu, 2007-11-22 at 14:26 -0800, SmileyChris wrote:
> On Nov 22, 10:48 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> > P.S. However I think you try to shoot yourself in the foot by tying
> > general unicode representation of an object to work only for HTML. I'd
> > rather leave it to some spec
On Wed, 2007-11-28 at 11:00 -0800, David Cramer wrote:
> I was debugging a query earlier and noticed that ManyToMany filter
> calls perform a left outer join.
>
> The only use case of this I could come up with is
> myfield__isnull=True. Are there any other reasons this is needed?
>
> If not I'd
I was debugging a query earlier and noticed that ManyToMany filter
calls perform a left outer join.
The only use case of this I could come up with is
myfield__isnull=True. Are there any other reasons this is needed?
If not I'd like to propose changing this to use INNER JOIN (on the
exception of
[ NOTE: I originally posted this to django-users but after looking at
the source code it occurred to me the solution is probably something
more fundamental to the core so I'm reposting it to dev and expanding
it a bit. Apologies for the duplication. ]
Say you're using Django to offer a public RES
On Nov 27, 4:05 pm, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> That why large companies have comittee's and auditors for.
>
Oh yes, I learned what a committee was for when I walked on to a job
which was a complete mess. Make it look like I was at fault, when they
were just buying cheap hardware f
12 matches
Mail list logo