sion about this previously? I haven't found any.
Thanks
Craig de Stigter
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send
could decide to break at any time.
But it's a better solution to certain problems than MTI is, and it doesn't
deserve the bashing that some people seem to give it. Use the right tool
for the job. If that's STI then use STI :)
Craig de Stigter
On Saturday, 7 June 2014 06:05:29 UTC+12, Aymeric Au
et/22690>. I'd love to see
better support for this in Django core.
Regards
Craig de Stigter
On Thursday, 22 May 2014 21:02:48 UTC+12, Anssi Kääriäinen wrote:
>
> On 05/22/2014 11:13 AM, Shai Berger wrote:
> >> Any thoughts on this idea?
> >>
> > Instinct
Just confirming that this fixed the memory leak problem for us. Thanks
again :)
On Friday, March 22, 2013 3:07:02 PM UTC+13, Craig de Stigter wrote:
>
> Karen Tracey saves the day!
>
> Thanks so much, seems likely that's it :)
>
> Craig de Stigter
>
> On Friday, March 22
Karen Tracey saves the day!
Thanks so much, seems likely that's it :)
Craig de Stigter
On Friday, March 22, 2013 2:25:04 PM UTC+13, Karen Tracey wrote:
>
> On Thu, Mar 21, 2013 at 9:00 PM, Craig de Stigter
> <crai...@gmail.com
> > wrote:
>
>> Hi everyone
>>
&g
he bug on a
dev server, and I'm not comfortable with doing `git bisect` on our
production box ;)
I've tried using Dozer to track down the leak but it appears to cause
apache to segfault with annoying regularity before finding anything of
consequence.
Any tips welcome
Thanks
Craig de Stigter
-
ter/LICENSE.txt>
to
the repo to clear up any confusion.
Would other devs be interested in adding something like django-typed-models
to Django core? What kinds of changes would make that more likely?
Cheers
Craig de Stigter
On Tue, Oct 30, 2012 at 2:34 AM, Krzysztof Jurewicz <
krzysz
reads those posts, as I haven't got a
response in 10 days.
Thanks
Craig de Stigter
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/s4smW
Since multi-table-inheritance is the only kind of inheritance (apart
from abstract/proxy) supported by Django's ORM, I don't know what
other type of inheritance django_polymorphic would be referring to...
As per my original post, I want to store everything in one table (all
subclasses have
Hi guys
Thanks for pointing those out. I knew I couldn't have been the first to want
this. I guess I just didn't know the right words to search for here.
It looks like django_polymorphic does what I want. I'm not yet sure why it
says it takes one query per type of model in a queryset. Unless
I realise everyone's been busy with getting 1.3 ready, but doesn't anyone
have thoughts on this? It's been two weeks ...
Thanks
Craig
On Thursday, February 17, 2011 11:08:57 PM UTC+13, Craig de Stigter wrote:
>
> Hi folks
>
> Ever since Django started supporting various ty
ly that you more
experienced gurus could illuminate?
Thanks in advance
Craig de Stigter
Maintainer of django-mptt and full time dev at koordinates.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, sen
12 matches
Mail list logo