Lars, have you made any progress on this? I agree that only the numeric types are interesting as multiple keys, so worrying about URL encoding is pointless (i.e., there's no reason to worry about supporting multiple arbitrary-string keys).
I'm trying to convince a team to use Django for new development on a large (1M+ records) existing database. The truth is it won't happen due to lack of this exact feature -- the existing database uses multiple (numeric) keys widely, in very conventional ways. When there are other non-Django interfaces still in use by users, adding special database id columns for Django's sake is unfeasible. Leo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
