If I allow the "created_on" columns to be nullable it kindda works. The second action I perform is performed succesfully, i.e. when I go back into the "Account" detail and add 2 more "Project" child objects.
When look at the data in the database I see that the created_on column has been left NULL on the 2 new records. mysql> select * from organizer_projects; +----+--------+------------+---------------------+---------------------+ | id | name | account_id | created_on | updated_on | +----+--------+------------+---------------------+---------------------+ | 1 | pluto | 1 | NULL | 2006-03-13 17:01:30 | | 2 | goofy | 1 | NULL | 2006-03-13 17:01:30 | | 3 | mickey | 1 | 2006-03-13 17:01:30 | 2006-03-13 17:01:30 | | 4 | mini | 1 | 2006-03-13 17:01:30 | 2006-03-13 17:01:30 | +----+--------+------------+---------------------+---------------------+ Is this a bug in the admin interface ? Many thanks, Ijonas Kisselbach, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
