Hmm... That sort of works, but not quite. If I use the filter method, it won't properly set the jumbledname on the first save. However, if I go back in and save the instance again a second time, it will properly set jumbledname. If I had it to guess, (after looking at the Django documentation) it's because the filter method uses a SQL like statement (rather than just evaluating the post data) which probably means it has to look at the database first...in other words, the first save changes the lastname field, and the second save looks at that field and changes jumbledname accordingly. (This is a guess, but based on the behavior, I think it's the right one). Any ideas as to how I might modify it?
Thank you for everything, bkev --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
