Hi, I think I was slightly misunderstood or my post left a false intention. My true purpose just was to say, that e.g. I am one of those who would like to see this as a core feature. I didn't meant to crack the whip ;-)
> It has been considered. It has been accepted. It just hasn't been > implemented. For all the noise about how essential this feature is, > very few people (Ben Ford, and a handful of others) have acutally > stepped up and offered to help. > > You obviously consider this to be a 'somewhat really important > feature'. However, that's your priority set. True. It is my priority. Well - and if it does not go into trunk I'd have tried in doing a merge by myself hoping to get it working somehow. > Code doesn't write itself, and we're all volunteers here. I know that. I'm a programmer myself and a volunteer in several projects, too. > If you > REALLYOMGMUSTHAVE this feature, pitch in and help. If you can't write > code, donate some cash to someone that can. If/when the multidb branch > reaches a state of maturity, and the design meets with the > satisfaction of the core developers, we would be only too happy to > merge it into trunk. Well - basically I'd like to help. I only fear of not having enough python acknowledge. I started python a few weeks ago and immediately jumped into the django-water. Kind regards Mario Adam P.S. Sorry again for maybe having sound like those typical "Write me these lines of code immediately"-customers. It wasn't meant this way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
