Issue 36 in deseb: foreign key table changed but field name did not : deseb did not recognize any change

[codesite...@google.com]

Status: New
Owner: ----

New issue 36 by crucialfelix: foreign key table changed but field name did
not : deseb did not recognize any change
http://code.google.com/p/deseb/issues/detail?id=36

this may be too complicated a change to handle correctly.

class AccountList(models.Model):

accounts = models.ManyToManyField(User)
... changed to:
accounts = models.ManyToManyField(Person)

so the join table changed, but the field name did not

I don't regard this as a major problem, and retitling field to persons is
better anyway.

I think a brief explanation about HOW the magic is performed would be very
helpful. the we can understand problems better.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 36 by burchik: foreign key table changed but field name

did not : deseb did not recognize any change
http://code.google.com/p/deseb/issues/detail?id=36

There are a lot of known limitations in current version of changes analyzer.
Current version has piles of magic, that's right.
I wrote much better version, but last time doesn't have any minute to write
front-end for it.

[codesite...@google.com]

Updates:
Status: Accepted

Comment #2 on issue 36 by burchik: foreign key table changed but field name

did not : deseb did not recognize any change
http://code.google.com/p/deseb/issues/detail?id=36

(No comment was entered for this change.)