Update fails

[wiktorwojcikowski]

Applying locking.0004_auto_20150915_1411...

django.db.utils.ProgrammingError: column "id" cannot be cast automatically to type uuid
HINT: Specify a USING expression to perform the conversion.

[wiktorwojcikowski]

I have recreate table with id field as UUIDField (by changing it in initial migration, and comment out migration 0004). Worked, but it still need a fix.

[nielsvanoch]

Good catch. I'll update this (probably some time this weekend).

[nielsvanoch]

I've pushed a version to https://github.com/vikingco/django-db-locking/compare/issue-24/uuid-migration. It works in the setups I've tried, but could you validate it on yours as well @wiktorwojcikowski? And if you should still have issues, what database (version) are you using?

[wiktorwojcikowski]

Works!
There are some warnnigs about thsi dates without timezones:
https://github.com/vikingco/django-db-locking/blob/issue-24/uuid-migration/locking/migrations/0003_optimize_queries.py#L19

RuntimeWarning: DateTimeField NonBlockingLock.renewed_on received a naive datetime (2015-09-07 03:32:18.056000) while time zone support is active.

But it works anyway. Thanks for fixing.
(I'm using postgresql 9.1)

[nielsvanoch]

Ok, great! I'll bump the version.

[wiktorwojcikowski]

Ok, locally worked but I test on dev server now and if there are any locks at DB, it throws "Duplicate entry" error, because all default uuids are same. I clear db and it pass, but it means it's still not perfect.