Thanks for the information!
Low level worked for me :-)
Keep up the good work!
>>MM
On Nov 20, 12:48 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2007-11-19 at 08:50 -0800, MichaelMartinides wrote:
> > Hi James,
>
> > I entirely understand your point.
>
> > But for users as me,
On Mon, 2007-11-19 at 08:50 -0800, MichaelMartinides wrote:
> Hi James,
>
> I entirely understand your point.
>
> But for users as me, it makes a difference to know if a feature is in
> very far distant or rather near future...
>
> I tried the branch it worked in command mode line as expected
Hi James,
I entirely understand your point.
But for users as me, it makes a difference to know if a feature is in
very far distant or rather near future...
I tried the branch it worked in command mode line as expected but gave
an error when I tried it in the browser, so I simply asked.
Cheers,
On 11/19/07, MichaelMartinides <[EMAIL PROTECTED]> wrote:
> Could anyone give me a hint when the queryset-refactor branch might be
> merged into the trunk?
When it's done.
I don't mean to speak on Malcolm's behalf here, but the frequency with
which "when will X merge into trunk" is asked warrant
On 11/19/07, MichaelMartinides <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Could anyone give me a hint when the queryset-refactor branch might be
> merged into the trunk?
In the last I recall seeing posted from Malcolm (
http://groups.google.com/group/django-users/msg/87f697435fcbe0d6) he's
target
Hi all,
Could anyone give me a hint when the queryset-refactor branch might be
merged into the trunk?
I'm not good at the extra() stuff for the creation of intersection
querys of manytomany fields.
In the current queryset-refactor filter(...).filter(...) on the
manytomany field seems to work gr
6 matches
Mail list logo
