On Thu, Feb 12, 2009 at 2:54 PM, Ludvig Ericson
<ludvig.eric...@gmail.com> wrote:It has consequences because you are proposing to change the order in
> Feb 11, Johan Bergström:
> I fail to see how "it has consequences for existing code", as Russell
which indexes and custom SQL are applied. Any code that depends on the
existing order will be affected.
> I did discuss this with Bergström, and we came to the conclusion thatIf it has the potential to break _any_ code, it is an unacceptable
> it won't actually break much code, if any.
change. The Django core developers have stated that we will maintain
backwards compatibility of the v1.0 interface, so any change with even
the _potential_ to affect backwards compatibility will need to be
checked very carefully.
However, the larger point is that you don't get to make that decision
> The only case which it could break, AFAICT, is if custom SQL managesThis is what needs to be confirmed, and given that it is a non-trivial
> to depend on the absence of indexes. I guess that could break code
> that violates indexing constraints, which are applied later, maybe? I
> don't know.
change, your decision needs to be confirmed by a core developer. I am
willing to be convinced, but you will need to prove to me that there
is no backwards compatibility problem here. The discussion in this
thread so far hasn't done that.
To answer the original question (why is it done in this order) -
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.