Re: [ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)

Tom, Create a view that accepts a "uri" argument and returns a 302 to the provided URI. Then, update your redirect_to callable to urlencode the URI and send them to /your/redirect/view/?uri=[encoded URI] and problem solved. -- You received this message because you are subscribed to the

Re: Oracle backend bug makes testing on oracle slower?

On Tuesday 11 December 2012, Florian Apolloner wrote: > On Tuesday, December 11, 2012 8:53:55 PM UTC+1, Shai Berger wrote: > > Should I open a ticket for it? It is a one-line patch... > > Please try to test this on master first, we most likely won't patch 1.3. > This was referring only to the

Re: Oracle backend bug makes testing on oracle slower?

On Tuesday, December 11, 2012 8:53:55 PM UTC+1, Shai Berger wrote: > > Should I open a ticket for it? It is a one-line patch... > Please try to test this on master first, we most likely won't patch 1.3. Cheers, Florian -- You received this message because you are subscribed to the Google

Re: Oracle backend bug makes testing on oracle slower?

On Tuesday 11 December 2012, Ian Kelly wrote: > On Tue, Dec 11, 2012 at 6:31 AM, Shai Berger wrote: > > Hi all, > > > > I've just been hit by a very simple and annoying bug on Oracle, on Django > > 1.3.4. Without testing, it seems to no longer be as bad on master, but a > >

Re: Oracle backend bug makes testing on oracle slower?

On Tue, Dec 11, 2012 at 6:31 AM, Shai Berger wrote: > Hi all, > > I've just been hit by a very simple and annoying bug on Oracle, on Django > 1.3.4. Without testing, it seems to no longer be as bad on master, but a shade > of it still remains. > > The bug is this: The

Re: About GSoC 2013

Hi Mayur -- You're a bit ahead of the curve here -- GSoC 2013 hasn't even been announced yet. Once it is, we would have to apply and be accepted. All in all, we won't know either way until around March. Jacob On Tue, Dec 11, 2012 at 10:31 AM, Mayur Patil wrote: > Hi

About GSoC 2013

Hi there, I want to ask is Django participating in the GSoC 2013?? Waiting for your Reply. -- *Cheers,* *Mayur.* -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: UUID Field really wontfix?

If someone can come up with a good patch I'd be fine considering it for core. Jacob On Tue, Dec 11, 2012 at 9:24 AM, Thomas Guettler wrote: > This ticket is closed since several years. Maybe it is time to think about > it again. > > Add UUID Field: >

Re: Single table inheritance - working implementation

On 7 joulu, 16:18, Krzysztof Jurewicz wrote: > On 29.10.2012 14:34, Krzysztof Jurewicz wrote: > > > In February, Craig de Stigter released django-typed-models > > , > > a package implementing

UUID Field really wontfix?

This ticket is closed since several years. Maybe it is time to think about it again. Add UUID Field: https://code.djangoproject.com/ticket/4682 Thomas Güttler -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because

Re: Possible bug with GenericRelations and values_list

For what its worth this one should be fixed in the patch for ticket #10790. After the patch the join condition will know the join field, and the join field will be asked for extra join sql when generating the join clause. This way it will be possible to append the content type restriction into the

Oracle backend bug makes testing on oracle slower?

Hi all, I've just been hit by a very simple and annoying bug on Oracle, on Django 1.3.4. Without testing, it seems to no longer be as bad on master, but a shade of it still remains. The bug is this: The DatabaseFeatures for the Oracle backend do not specify that it supports transactions. On

Custom ordering using SQL backend

Hi all, I recently solved a problem with a field that could not be ordered as I wanted. It was a CharField containing of exactly seven numbers like 990, 010, 120 etc. The first two digits indicated a year (99 being 1999 and 12 being 2012). The ordering should be different from

Re: [ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)

On Mon, Dec 10, 2012 at 10:38 PM, James Bennett wrote: > Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued > in response to security issues. > > Details are available here: > > https://www.djangoproject.com/weblog/2012/dec/10/security/ > Is the second