Status of bug #11580 ?

[Michał Nowotka]

Hello,
There is a bug submitted 3 years ago:

https://code.djangoproject.com/ticket/11580

I have exact the same problem using django 1.4.

Are there any plans to fix that in near future?

[Russell Keith-Magee]

Hi Michał,

You posted exactly the same question to Django-dev yesterday, and Florian answered that question 2 hours after you posted it. Reposting exactly the same question to a different mailing list isn't very helpful, and it won't change the answer.

Yes, the bug is 3 years old. It will be fixed when someone volunteers to fix it. So far, nobody has volunteered.

If this is a bug that is affecting you, then might I suggest that *you* should volunteer to fix it. 

Yours,

Russ Magee %-)

--

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

[Michał Nowotka]

OK, so first of all I'm new to both lists. I already asked some questions here and usually I get email with my question 5 minutes after post (I mean my original question not the answer). I was waiting long and I though my question didn't pass moderation so maybe it would be better to ask it on probably less strict django-users group. So my apologies for my impatience.

Now about  the bug itself. Although there is not any patch attached to this bug report you can find it in the text.  The filed_cast_sql function should be changed from:

        def field_cast_sql(self, db_type):
        if db_type and db_type.endswith('LOB'):
            return "DBMS_LOB.SUBSTR(%s)"
        else:
            return "%s"

 to:

        def field_cast_sql(self, db_type):
            return "%s"

or even completely removed. Since this is trivial it's only a matter of including this small change in core. I don't have such privileges that's why I'm asking you to do it.

Kind regards,
Michal Nowotka

[Tomas Ehrlich]

Hi Michał,
actually, you *do have* such a privilege. Simply clone development
version of django, fix the file with bug, test it, and post patch to
ticket you've mentioned.

If you include test which check, that your patch really fix the bug,
core developers will pull in into repository soon.

It's really that easy and for you it would be dead easy, since you
already know the solution.

Take a look at
https://docs.djangoproject.com/en/dev/internals/contributing/


Cheers,
Tom

Dne Wed, 7 Nov 2012 09:13:33 +0000
Michał Nowotka <mmm...@gmail.com> napsal(a):

S pozdravem
Tomáš Ehrlich

Email: tomas....@gmail.com
Tel: +420 608 219 889
Jabber: elv...@jabber.cz

"Půjdu kamkoliv, pokud je to kupředu." - J. London