On Mon, May 11, 2009 at 1:22 PM, NoviceSortOf <dljonsson2...@gmail.com>wrote:
> Now get this -- if I add a 'return' to the end of the function it adds > the rows -- why is this? > This, combined with the sequence number increasing but being unable to actually see rows added, makes me think perhaps without the return wherever you have added it the code is going down some path that is causing the transaction you are in to be rolled back instead of being committed. > > If I insert an assert False the functions sort of behave like they are > working returning an object for the new pk id but incrementing the seq > tables, but not loading the data into postgresql. > > any idea why this is? > Does your Django view use the commit_on_success decorator? Or are you doing manual transaction management and somehow not committing the transaction? That would cause the transaction to be rolled back in the case of any error (which an assert False would trigger). I'd have to check (which I don't have time for at the moment) but I think Postgres is one of the DBs where rollback doesn't affect sequence numbers that have been incremented during a transaction, which would explain why you see that incrementing without seeing the actual objects being saved. 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
