I'm not endorsing any specific set of changes here, but I can address the
feasibility of making the changes in Trac:
>From empirical testing on my own Trac installation (running 0.11 currently,
Django is on 0.12) updates to components, resolutions, etc. all propagate
correctly when edited through the admin. Whether that's because Trac's
backend is using foreignkeys (as one might hope), or whether it's simply
wired up with the right hooks to update the database fields when the values
are edited I don't know. But either way, it works as you'd expect.
So, whatever changes we decide to make, they shouldn't be hard to implement.
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
