Oops - posted too quickly - the lack of change to the DB is actually a more recent manifestation.
From the code posted, the 'not working' issue was just that the print statements wouldn't yield any output on the console at all. I guess when django has trouble with the code it ignores it and moves on. There was no traceback though either, making debugging a bit tough. R. On Jul 7, 10:14 am, RossGK <[EMAIL PROTECTED]> wrote: > Sorry - the issue is that no change occurs to the database - I am > using pgAdminIII to inspect the database, and so can see if an entry > gets created in my table. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
