First time {% thumbnail .... %} is called it fails with IntegrityError

[smileychris]

First time {% thumbnail .... %} is called it fails with IntegrityError

[SmileyChris]

Hi pigletto - it sounds like you haven't run the south migrations. Storage is no longer a separate table.

If you're using mysql though, I think the migrations are screwed up. You'll want to follow issue 45 if that's the case.

[pigletto]

I did a fresh install of easy_thumbnails. I did both syncd and migrate and I use PostgreSQL.
After running syncdb and migrate (no errors) I have these tables in database: easy_thumnbails_source, easy_thumnbails_storage and easy_thumbnails_thumbnail. The storage_id (integer not null) column exists in easy_thumbnails_source.

You say that there is no longer separate table for storage, but from migration files it seems to me that:

1. migration 0003 creates table storage_new
2. migration 0009 deletes table storage
3. migration 0010 renames storage_new to storage

so there still exists storage table.

I've looked into issue 45 and checked code for migration: 0010_rename_storage.py.
Seems to me that foreign key to storage is only removed for mysql now.

[SmileyChris]

Thanks for your investigations. It does seem like I lost a very important migration somewhere along the way :-/

In any case, I've just pushed a change (35d1d3f) which adds in migration 0013 that should get the definitions to where they should be.