Display link to change-form on inlines where model is registered in admin site

I've just submitted #13163 [1] with a patch to display a link to the full change-form for inlines of models which are registered in the same admin site, similar to the existing "view on site" link for inlines. I have had numerous projects where this would have been immensely useful (for which I

Re: GSoC10 Idea: Additional queryset methods

On Fri, 2010-03-19 at 05:39 -0700, Sh4wn wrote: [..] > I want to refactor the QuerySet and other databases related API's, > which adds an additional method of selecting records, and provides > more control of what data you'll select, but probably is a bit more > complex than the current API. It's

Re: GSoC10 Idea: Additional queryset methods

I will only add new things, and won't break any current API. Why this is needed: You can actually do *database independent* queries with full control. The current API is IMO limited when trying to execute queries with joins. Especially when you want to aggregate data from the joined table. Yes,

Re: GSoC10 Idea: Additional queryset methods

On Fri, Mar 19, 2010 at 11:09 AM, Karen Tracey wrote: > However, it does seem to be in direct conflict with the idea of getting to > the ORM working on non-SQL databases. The additional methods mentioned > (select, from, leftJoin) together all sound like they are moving the

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

Because of this thread I decided to release a little app we have been using internally. It's a straightforward way to modify the default site object. More details: http://oppian.com/labs/django-defaultsite/ Any comments/suggestions welcome. Sincerely Matthew Jacobi Oppian Systems Ltd On Mar

Re: GSoC10 Idea: Additional queryset methods

On Fri, Mar 19, 2010 at 10:47 AM, Jacob Kaplan-Moss wrote: > On Fri, Mar 19, 2010 at 7:39 AM, Sh4wn wrote: > > I want to refactor the QuerySet and other databases related API's, > > which adds an additional method of selecting records, and provides > >

Re: GSoC10 Idea: Additional queryset methods

On Fri, Mar 19, 2010 at 7:39 AM, Sh4wn wrote: > I want to refactor the QuerySet and other databases related API's, > which adds an additional method of selecting records, and provides > more control of what data you'll select, but probably is a bit more > complex than the

Re: GSoC10 Idea: Additional queryset methods

What would be the difference with the new raw method on manager (http://docs.djangoproject.com/en/dev/topics/db/sql/#django.db.models.Manager.raw)? -- Gert Mobile: +32 498725202 Web: http://gert.selentic.net On Fri, Mar 19, 2010 at 13:39, Sh4wn wrote: > ## The Django

GSoC10 Idea: Additional queryset methods

## The Django ORM ### The Problem Django is a awesome webframework, and works quite well. But after using it for about a year now, I've came across some annoyances. One great thing of django is the amount of third party reusable apps, unfortunately, this comes at a cost in the number of database