Why the request.get_full_path() returns empty string

[Eratothene]

Does any have I idea why is that so in trunk?
def get_full_path():
return ''

Docs say:
get_full_path()
Returns the path, plus an appended query string, if applicable.

Example: "/music/bands/the_beatles/?print=true"


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Why the request.get_full_path() returns empty string

[Eratothene]

Don't bother I have just figured out why.

On 10 дек, 07:07, Eratothene <[EMAIL PROTECTED]> wrote:
> Does any have I idea why is that so in trunk?
> def get_full_path():
> return ''
>
> Docs say:
> get_full_path()
> Returns the path, plus an appended query string, if applicable.
>
> Example: "/music/bands/the_beatles/?print=true"
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: [GSoC] Aggregate Support to the ORM

[Eratothene]

It looks that API lacks support for SQL HAVING clause, this one should
be distinct from filter, GROUP BY without HAVING is often useless.

Consider adding it to api (something like
Model.objects.aggregate(height__sum).having(sex='M'))

Also do not forget to add HAVING clause to .extra()  method.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Multiple database support

[Eratothene]

I think there is a third issue.

Usage of several RDBMS in one django application simulatneously

For example we maintain two RDBMS: monetdb and postgresql. The latest
and most accessed data is stored in monetdb for performance. After one
month data is moved to posgresql which holds the full archive.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---