Hi Folks, I'm aware that foreign key fields such as manytomany don't update during the save() method of Model, and that there are some issues surrounding relations to 'self'. I have a model which has a couple of utility functions to update two such relations, and I've found that they don't do anything if I call them during Model.save() - perhaps because the SQL is executed out of order, or some nuance of the sql cursor behavior?
I've also tried using signals and the save_model call of AdminModel, none of them have any effect. self-relations only seem to update in a separate request. Also note that all the relevant primary keys exist already. My setup is almost a clean install of the latest django. I haven't changed the transaction stuff. It's the latest mysql, Python 2.5 on OS X 10.5. I am wondering if perhaps there is some asynchronous db stuff going on? Perhaps I could force it to flush before I run my update methods? thanks, David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
