On Tuesday 21 May 2013 22:11:02 Aymeric Augustin wrote:
> On 19 mai 2013, at 15:33, Shai Berger <[email protected]> wrote:
> >
> > So -- I want to fix, now, the thing that was, well, not broken, but bent,
> > in 2007. And my question to you -- especially, those of you who
> > participated in the boulder sprint -- can you think of any reason why I
> > shouldn't?
>
> Based on the impressive amount of research you've performed, and on the
> facts you've found, I think you can go ahead and simplify the code.
>
My understanding is that an overridable method in the base DatabaeOperations
constitutes a public interface (for 3rd party backends). It is not documented,
so I guess we can get away with skipping deprecation cycles; but don't you
think we should try to warn users who override it that it is no longer used?
> I'll review the patch if you want. Thanks for working on this.
Thanks, I think I'll call you up on that one. For now, I just removed the
Oracle override, to let it pass some more tests.
Have fun,
Shai.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
