On Thu, Oct 9, 2008 at 5:59 PM, Hancock, David (dhancock) < [EMAIL PROTECTED]> wrote:
> I've found that using raw_id_fields saves a lot of time for our users > over loading an entire many-to-many select. (But for shorter lists, the > many-to-many widget is by far the best interface I've seen for multiple > selections.) > > There's an aspect of the raw_id_fields (this is in the admin interface) > that is unsettling to the users, though. On a normal foreign-key > relationship, it works great. But here's a scenario where it's not so good > for the many-to-many relationship. A trip leg can have several travelers. If > you open that leg to add a traveler, you see the list of IDs and a little > magnifying glass. Click the glass to add another traveler, click the one one > you, and it's added to the list. If you click the magnifying glass, > determine that you need to add a NEW traveler from that index list, and then > save the traveler, it's populated back on the original leg page as the sole > ID in the travelers field. (That is, all the IDs previously in that field > are overwritten.) > > This seems like a bug to me, but if someone can set me straight on how it > should work, I'd be grateful. > It sounds like a bug to me and worth a ticket so it's not forgotten, assuming a search of the tracker doesn't reveal any similar reports. Sample (simple) models with a detailed recreation recipe are always appreciated in tickets. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
