On Thu, 2009-04-09 at 20:48 -0700, jameslon...@gmail.com wrote:
> I have a dynamically generated search form which constructs Q()
> objects at runtime. This works brilliantly in almost every case. There
> is a particular combination of these objects which appears to create
> an extra where clause
I recently checked out coverage.py in more depth, and it seems to have a
much more current effort behind it, so I'm comfortable using it for coverage
integration.
As for someone to work with on GSoC, I'm not saying it has to be anyone, the
more the better. I think the deciding factor is the mento
I have a dynamically generated search form which constructs Q()
objects at runtime. This works brilliantly in almost every case. There
is a particular combination of these objects which appears to create
an extra where clause though. Currently this isn't killing me because
the clause is simply a d
George Song wrote:
> On 4/7/2009 11:25 AM, Kevin Kubasik wrote:
>
>> I actually proposed this as part of my GSoC project. I think there is
>> enough interest that basic coverage support could be seen in core.
>>
>
> I agree and have had some quick emails with Jacob about this. I think
> the
StumbleUpon
Discover your web
Popular Websites
http://www.stumbleupon.com/redirect.php?t=j&u=18579502&d=http%3A%2F%2Fbuzz.stumbleupon.com%2F&l=6&c=2ifadp4ljy0zsmxz
People Online Now
http://www.stumbleupon.com/redirect.php?t=j&u=18579502&d=http%3A%2F%2Fwww.stumbleupon.com%2Fpeople%2F&l=6&c=2ifadp
On Fri, Apr 10, 2009 at 12:05 AM, Sebastian wrote:
>
> Rory and I have applied patch 6646 to our Django installation (1.0-
> final-SVN-unknown). Although the patch works as described, the
> following no longer works:
>
> if the included template also 'extends' from a base template the
> following
On Thu, 2009-04-09 at 12:46 -0400, Steve wrote:
> Hello Djeople,
>
> Trolling for criticism, broader use-cases, or a lurking solution for
> my latest problem: Say you've got a model with two fields
> 'primary_lang' and 'secondary_lang' and you'd like to filter across
> them in one fell swoop. The
On Thu, 2009-04-09 at 14:31 -0700, Adys wrote:
> http://groups.google.com/group/django-developers/browse_thread/thread/87aae5cbd60bb904/505f3bd962711db7?hl=en
>
> You wanted an use case, someone else just provided you with it.
No they didn't. There's still an unanswered request in that thread to
On Thu, Apr 9, 2009 at 6:22 PM, Stephen wrote:
>
> Excellent, I'll be on the lookout for the discussion. For the sake of
> history here's my hack-around:
>
> http://www.djangosnippets.org/snippets/1423/
>
> Essentially just a sub-class of ModelManager with an additional
> convention of looking fo
Excellent, I'll be on the lookout for the discussion. For the sake of
history here's my hack-around:
http://www.djangosnippets.org/snippets/1423/
Essentially just a sub-class of ModelManager with an additional
convention of looking for foo_filter() methods in the event it hits a
FieldError while
http://groups.google.com/group/django-developers/browse_thread/thread/87aae5cbd60bb904/505f3bd962711db7?hl=en
You wanted an use case, someone else just provided you with it.
"Why do you care so much about the index being there, anyway? It
should only
affect you badly under quite extreme circumst
On Thursday 09 April 2009, MS wrote:
>
> > INDEX
> >
> > > Such 'foreign key' constraints create indexes in database (at least
> > > mysql).
> >
> > Have you "snipped" the SQL that creates indexes? I see no indexes
> > being created here. I see a constraint. Am I missing something?
>
>
[demonstati
On Thu, Apr 9, 2009 at 12:46 PM, Steve wrote:
> Hello Djeople,
>
> Trolling for criticism, broader use-cases, or a lurking solution for my
> latest problem: Say you've got a model with two fields 'primary_lang' and
> 'secondary_lang' and you'd like to filter across them in one fell swoop. The
> o
Rory and I have applied patch 6646 to our Django installation (1.0-
final-SVN-unknown). Although the patch works as described, the
following no longer works:
if the included template also 'extends' from a base template the
following error occurs:
Exception Type: TemplateSyntaxError
Excep
Hello Djeople,
Trolling for criticism, broader use-cases, or a lurking solution for my
latest problem: Say you've got a model with two fields 'primary_lang' and
'secondary_lang' and you'd like to filter across them in one fell swoop. The
obvious solution is to make a manager method filterlang('foo
On Wednesday 01 April 2009 00:10:01 Jacob Kaplan-Moss wrote:
> An even bigger problem would be for users of third-party reusable
> apps: my personal blog is a mere 645 lines of code, but there's
> over 10,000 lines of third-party apps I'm building on top of. If I
> want to upgrade to 1.1 and keep
On Thu, Apr 9, 2009 at 5:02 AM, Jeremy Dunck wrote:
>
> On Tue, Mar 31, 2009 at 5:47 PM, Malcolm Tredinnick
> wrote:
>>
>> On Tue, 2009-03-31 at 14:48 -0500, Jeremy Dunck wrote:
> ...
>>> I'm aware of ticket #7539, but would prefer to keep the scope narrower
>>> and ask the hopefully-useful ques
Hi,
> UNIQUE CONSTRAINT
>
> If you removed the unique constraint from OneToOneFields, what would
> you get?
>
> You'd get a ForeignKey.
>
> Therefore removing the 'unique' constraint makes no sense whatsoever.
>
> If you believe you do not want a unique constraint, ask yourself why
> you desire t
18 matches
Mail list logo
