Hello Malcolm, On Oct 11, 4:20 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > ForeignKey(unique=True) >
I will try it this way & hope it works exactly as I need it to. Thank you for reading carefully my Email :-) My main point was not to criticize Django but to understand if there are other ways to do things I need to do. > The guiding principle is that we don't spend any real amounts of time > working on things that are already slated for removal or replacement. We > are pretty consistent in that. We want to have model inheritance and we > are writing newforms-admin. So we (core devs and a lot of other people) > aren't spending time on workarounds -- instead focusing on driving > towards those goals (along with our 570 other high priority items). Absolutely agree with that, and I understand it well. The only question which I also raised is about trac/tickets. IMO, if issue is about current trunk, and if its not fixed yet, closing it as 'wontfix'... Hm. May be we should have specific state for: "to be fixed in futurre". --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
