Re: future of QuerySet.extra()?

2015-08-03 Thread Tai Lee
I think that while `extra()` gets a bad rap, it is extremely useful when creating generic pluggable apps, and I for one would miss it if it were to be removed. In a comment on #7231 a few years ago I wrote: I can't reply to the discussion linked on Google Groups anymore, but wanted > to add my

Re: Setting up Django Over Apache Web-server

2015-08-03 Thread gilberto dos santos alves
hi. if you have cpanel see [1] or another similiar shared host plan. [1] http://support.hostgator.com/articles/django-with-fastcgi 2015-08-03 20:36 GMT-03:00 Mudassar Hashmi : > Please help to upload django on apache web server with without terminal > access to web server. > > Regards, > > Mudas

Re: future of QuerySet.extra()?

2015-08-03 Thread Josh Smeaton
Can you explain/give an example of grouping over non relations? I'll see if I can translate that to expressions in their current form. On Tuesday, 4 August 2015 07:10:05 UTC+10, Shai Berger wrote: > > On Monday 03 August 2015 10:27:14 Anssi Kääriäinen wrote: > > You can annotate raw SQL with ex

Setting up Django Over Apache Web-server

2015-08-03 Thread Mudassar Hashmi
Please help to upload django on apache web server with without terminal access to web server. Regards, Mudassar Hashmi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" gr

Re: future of QuerySet.extra()?

2015-08-03 Thread Shai Berger
On Monday 03 August 2015 10:27:14 Anssi Kääriäinen wrote: > You can annotate raw SQL with expressions. I think the only case that can't > be done with expressions is addition of extra tables to the query. Also grouping over non-relations, if I am not mistaken. Shai.

Re: future of QuerySet.extra()?

2015-08-03 Thread Tim Graham
Thanks! Here's a polished version of that: https://github.com/django/django/pull/5095 Let me know if it makes sense. On Monday, August 3, 2015 at 9:10:00 AM UTC-4, Anssi Kääriäinen wrote: > > On Mon, Aug 3, 2015 at 2:07 PM, Tim Graham > wrote: > > Is there an example we could give in the docs

Re: default values on database level

2015-08-03 Thread Michael Manfre
On Mon, Aug 3, 2015 at 9:25 AM, Podrigal, Aron wrote: > > > - Do we want to allow extending this to defaults that are applied on > every save (automatic database backed modified timestamps for example)? > > +1 for this one too. > This behavior would be a nice step toward computed (readonly) dat

Re: default values on database level

2015-08-03 Thread Podrigal, Aron
On Aug 3, 2015 3:36 AM, "Anssi Kääriäinen" wrote: > > On Wednesday, July 29, 2015 at 8:05:10 AM UTC+3, Aron Podrigal wrote: >> >> I would like to propose making Fields.default to rely on the database generated defaults where possible. This could be implemented by having some constants like fields

Re: future of QuerySet.extra()?

2015-08-03 Thread Anssi Kääriäinen
On Mon, Aug 3, 2015 at 2:07 PM, Tim Graham wrote: > Is there an example we could give in the docs to point readers in that > direction? There doesn't seem to be direct documentation about RawSQL expression. The RawSQL is once mentioned in the documentionation, but it definitely needs a bit more i

Re: Field.get_flatchoices seems to never get used

2015-08-03 Thread Tim Graham
Fixed in https://github.com/django/django/pull/5093, thanks for the report. On Sunday, August 2, 2015 at 12:48:13 PM UTC-4, Collin Anderson wrote: > > That looks right to me. > > On Sun, Aug 2, 2015 at 11:51 AM, Andy Baker > wrote: > >> I'll file a ticket but I wanted a quick sanity check first.

Re: future of QuerySet.extra()?

2015-08-03 Thread Tim Graham
Is there an example we could give in the docs to point readers in that direction? On Monday, August 3, 2015 at 3:27:14 AM UTC-4, Anssi Kääriäinen wrote: > > You can annotate raw SQL with expressions. I think the only case that > can't be done with expressions is addition of extra tables to the q

Re: default values on database level

2015-08-03 Thread Anssi Kääriäinen
On Wednesday, July 29, 2015 at 8:05:10 AM UTC+3, Aron Podrigal wrote: > > I would like to propose making Fields.default to rely on the database > generated defaults where possible. This could be implemented by having > some constants like fields.CURRENT_TIMESTAMP, etc. The tricky part here > i

Re: future of QuerySet.extra()?

2015-08-03 Thread Anssi Kääriäinen
+1 - Anssi On Friday, July 31, 2015 at 11:00:01 PM UTC+3, Tim Graham wrote: > > I had in mind a documentation note like this: > > Use this method as a last resort > > > This is an old API that we aim to deprecate at some point in the future. > Use it only if you cannot express your query using

Re: future of QuerySet.extra()?

2015-08-03 Thread Anssi Kääriäinen
You can annotate raw SQL with expressions. I think the only case that can't be done with expressions is addition of extra tables to the query. I am certain we will get a solution to this too in future releases. - Anssi On Friday, July 31, 2015 at 9:01:45 PM UTC+3, Andres Osinski wrote: > > Wou