On May 15, 8:12 pm, Russell Keith-Magee <[email protected]>
wrote:
> On Sat, May 16, 2009 at 5:27 AM, Mike Driscoll <[email protected]> wrote:
>
> > Hi,
>
> > I posted about this over a year ago and Jacob Kaplan-Moss said that
> > Django would eventually getcompositekey support, but he didn't know
> > when. Has anything changed? I dug around for SqlAlchemy+Django links,
> > but they seem to be the same as last year, except deader.
>
> Well, Jacob's advice is still accurate. Django will eventually
> getcompositekey support, but we don't know when :-)
>
> Compositekey support is "one of those features", like Multi-db
> support and schema evolution. Everybody seems to want it, but so far,
> nobody has been willing or able to put the time into implementing it.
>
> The core developers are all volunteers, so our time is limited, and so
> far, other features have taken priority. To whit - there have been
> 1829 checkins, making 73919 insertions and 28301 deletions to 849
> files in the 8 months since v1.0 was released.
>
> The other way this could get done is if someone from the community
> were to step up to the plate to implement the feature - and more
> importantly, to work with the core team to get an implementation from
> "working, but has some problems" to "ready for checkin". So far, this
> hasn't happened.
>
> If you wait long enough, one of the core team will eventually get
> around to implementingcompositeprimary key support. However, there
> are no guarantees on the timeline for this - there are plenty of other
> features that are begging to be implemented.
>
> The good news is that this is a volunteer open-source project. If you
> _really_ needcompositesupport, then you can push up your sleeves and
> start writing code yourself, or you can find someone for who is
> willing to exchange legal tender for working code. I'm lead to believe
> there are many such people in the world :-)
>
> Yours,
> Russ Magee %-)
Oops...I lost track of this thread when I went on vacation. I figured
this was the story. Unfortunately, my understanding of the current
Python web kits are at such a low level, I would probably be more
trouble than I'm worth. If the guys over on the TurboGears list
continue to ignore my questions on how to do multi-database
connections, then I may come back to this as I think Django has a
better community and documentation.
Thanks!
Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---