Re: A second stab at an implementation of composite fields

On Fri, Apr 12, 2013 at 07:35:45AM -0700, Anssi Kääriäinen wrote: > On 12 huhti, 16:44, Michal Petrucha wrote: > ForeignKeys have been changed a lot since 2012-11-04. The introduction > of ForeignObject (which is base for ForeignKey) means that there is > support for

GSoC 2013 - New and improved!

I'm very pleased to announce that Django is part of Google Summer of Code once again - and that this year, we're widening the scope of the kinds of projects we'll be accepting. In past years, we've only accepted projects working on Django itself, and while this has resulted in some very useful

Re: A second stab at an implementation of composite fields

On 12 huhti, 16:44, Michal Petrucha wrote: > As far as relationship fields go, we tried to ignore them at first and > get back to them during the second half of GSoC. Two approaches were > considered, one was to special-case CompositeField targets in > ForeignKey and in

Re: Support for WSGI applications within Django (Ticket #12091)

Hi Jacob, On Friday, April 12, 2013 3:09:40 PM UTC+1, Jacob Kaplan-Moss wrote: > > On Fri, Apr 12, 2013 at 8:54 AM, Gustavo Narea > wrote: > > So I guess that means that it won't be considered for inclusion in > Django? > > If so, I'll close that ticket. > >

Re: Support for WSGI applications within Django (Ticket #12091)

On Fri, Apr 12, 2013 at 8:54 AM, Gustavo Narea wrote: > So I guess that means that it won't be considered for inclusion in Django? > If so, I'll close that ticket. Hm, I wouldn't be so hasty -- it's something I, at least, would like to include. Of course, the

Re: Support for WSGI applications within Django (Ticket #12091)

Hello, Carl and Alex, You're right: Apart from not being able to embed Django sites, there's nothing preventing twod.wsgi from working with Django as it is now. So I guess that means that it won't be considered for inclusion in Django? If so, I'll close that ticket. Cheers, - Gustavo. On

[GSoC 2013] A second stab at an implementation of composite fields

Hello everyone, Hopefully some of you still remember me as the guy who's been trying to implement support for composite primary keys by means of composite model fields. I haven't provided a whole lot of information on the progress of this project for... quite a long time, so I'll try to rectify

annotate Count with special condition

Hi, I ran in this today. Say i have these two models in my app called atest class Person(models.Model): name = models.CharField(max_length=255) age = models.IntegerField(null=True) class Car(models.Model): owner = models.ForeignKey('Person', related_name='cars') brand =