On Mon, 2008-02-25 at 13:33 -0800, Mike Driscoll wrote: > Hi, > > I am doing research on alternative Python Web Frameworks that I can > use at my place of work. We use legacy SQL Server and have many > databases from various vendors which include composite (multi-column) > primary keys of the non-integer variety. Does anyone know how Ticket > 373 is coming along or if the SqlAlchemy branch of Django is getting > any love? The ticket doesn't seem to have any new data since approx. 4 > months ago (see http://code.djangoproject.com/wiki/MultipleColumnPrimaryKeys) > and I can't find much of anything newer than March 2007 for the > SqlAlchemy branch. > > Anyone know what's going on? I've been messing with TurboGears for a > couple of weeks, but their SqlAlchemy implementation doesn't seem to > play nice with MS SQL Server.
Multi-column primary keys is something we'll have one day, but maybe not in the immediate future. The problem is that it's very hard to make it work in a backwards compatible way. The first 75% is really easy, but then you have to make it work with generic relations and admin logs and things like that and you realise that the last 25% is about 90% of the work. I've started writing some code to implement them, but keep coming up against that hurdle, so I've put it off for a bit. Search the recent archives of this list for information about an external SQLAlchemy integration. The branch in Django's subversion repository isn't being maintained. Malcolm -- Borrow from a pessimist - they don't expect it back. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
