On Friday, August 31, 2012 12:10:54 AM UTC-6, Amyth wrote: > > Hey Jon, > > I guess this is because of a bug in django. Django already has a open > ticket for this bug. Check it out > here<https://code.djangoproject.com/ticket/17015> > . > > As described in that ticket, the reason for the problem is probably just that the Django user does not have the CREATE TRIGGER privilege, which it needs. The bug in Django is just that this condition is not detected and reported at the time the table is created, instead of getting a rather more obscure error message at the time the table is populated.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/BKHoqoZkF6oJ. 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.
