Re: Improving aggregate support (#14030)

Hi Michael, Thanks for taking a look, much appreciated. I haven't created a PR yet because I've rebased on top of Ansii's Lookups refactor which hasn't hit Master yet (and is changing slightly based on feedback of his PR). To answer your questions: Why were the aggregate specific fields,

Re: Website integrated mobile app for disaster

Hi Akanksha, We haven't started the GSoC process internally yet, so we haven't put together a collection of sample projects for this year; but if you want to see what we recommended last year, it's on our Wiki: https://code.djangoproject.com/wiki/SummerOfCode2013 Out of those projects, the

Re: Improving aggregate support (#14030)

With minor tweaks to django-mssql's SQLCompiler, I am able to pass the aggregation and aggregation_regress tests. If you create the pull request, comments can be attached to specific lines of code. I haven't had time to do a full review of your changes, but my initial questions and comments are:

Re: Migrations and swappable models/AUTH_USER_MODEL

Good points. Regarding 1), I can't specially control reconstruction of fields from migrations and raise errors only in that case - it's just calling the normal __init__. Since I'm going to have to write out a call to settings.AUTH_USER_MODEL anyway - the whole point of swappable=True is so the

Re: python querry on firebug extention .

Please don't crosspost to both django-developers and django-users. The topic of this list is the development of Django itself, django-users is for usage questions, although it's not clear to me how this question is related to Django. On Saturday, January 11, 2014 1:18:00 PM UTC-5, JAI PRAKASH

Re: Migrations and swappable models/AUTH_USER_MODEL

On Thursday 09 January 2014 01:10:09 Raphaël Barrois wrote: > On Wed, 8 Jan 2014 20:27:54 +0200 > > Shai Berger wrote: > > as people already use auth.get_user_model() -- so, you can > > monkeypatch *that* when generating migrations, and let them just keep > > doing what they

Re: Migrations and swappable models/AUTH_USER_MODEL

On Saturday 11 January 2014 11:45:55 Andrew Godwin wrote: > OK, I like that approach Russ - an inverted 1b. It'll be a bit harder to > explain in the docs, but it won't catch anyone out unawares, which is the > key thing. > I like it too. And foot-in-mouth re referencing swappables

Re: Feature request: post/pre commit/rollback signals

On 11 janv. 2014, at 11:05, Andrey Antukh wrote: > In my opinion, "the default case are solved with atomic block" seems to be a > workaround instead of a solution. As a short reminder, we’re talking about inconsistencies that arise when: 1) you do something in the database; 2)

python querry on firebug extention .

hello i am working on selenium module of python, i know how to make extension of firebug with selenium, but i want to know how to use firebug extension with request module / mechanize . i search a lot but unable to find it , please help . technique similar like :- from selenium

Re: Website integrated mobile app for disaster

Thankyou so much for your guidance sir! i m looking forward to present my ideas for improvement of django. However it would be great if you all could please suggest me with some ideas regarding SoC. Waiting for your reply eagerly and to work for the very same too. On Friday, January 10, 2014

Re: Migrations and swappable models/AUTH_USER_MODEL

OK, I like that approach Russ - an inverted 1b. It'll be a bit harder to explain in the docs, but it won't catch anyone out unawares, which is the key thing. Andrew On Thu, Jan 9, 2014 at 1:28 AM, Russell Keith-Magee wrote: > > > > On Thu, Jan 9, 2014 at 12:04 AM,

Re: Feature request: post/pre commit/rollback signals

Hi! In my opinion, "the default case are solved with atomic block" seems to be a workaround instead of a solution. I understand that signals in general are evil and register global callbacks is not a very good solution, but I think, that a orm should give some generic facility to attach code to

Re: Improving aggregate support (#14030)

A milestone has been reached. The diff is here: https://github.com/jarshwah/django/compare/akaariai:lookups_3...aggregates-14030?expand=1 - Existing annotations and aggregations working as they were - Complex annotations and complex aggregations now work - Complex annotations can now be