Re: Simple History - Field Change

No problem at all, glad you got it sorted! Cal On Sat, Jul 5, 2014 at 6:32 AM, Aaron Reabow wrote: > You are totally right. > > There is a historical table that required deletion. > > This is why you shouldn't debug late on friday afternoon. I had actually > looked for that

Re: Simple History - Field Change

You are totally right. There is a historical table that required deletion. This is why you shouldn't debug late on friday afternoon. I had actually looked for that table but somehow missed it. I will pick up the broader problems with simple history separately. thanks for taking the time to

Re: Simple History - Field Change

It sounds like you haven't applied the table changes to the cloned table which it creates to track changes. I'd advice using something like South to manage your schema changes, and this should work out of the box with django-simple-history. For now, you can delete the cloned table and re-sync,

Re: Simple History - Field Change

Environment: Request Method: POST Request URL: upon request :) Django Version: 1.6.2 Python Version: 2.7.5 Installed Applications: ('django.contrib.admin', 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.sites', 'django.contrib.contenttypes', 'django.contrib.sessions',

Re: Simple History - Field Change

Can you please paste the full clear text stacktrace? Cal On Fri, Jul 4, 2014 at 3:49 PM, Aaron Reabow wrote: > Hi all, > > I am getting this error on a modelform > > smallint out of range > > > > But the form is actually submitting just fine and being stored in the DB. I >