StateLog can't handle non-numeric object_id

[destos]

Ran into this issue when attempting to log state changes on a model that uses Postgres uuid4 fields for the primary key.

[tysonclugg]

Thanks for the report @destos. 😃

Looking through https://docs.djangoproject.com/en/1.8/ref/contrib/contenttypes/#generic-relations in the section titled "Primary key type compatibility" I found this:

There is no one-size-fits-all solution for which field type is best. You should evaluate the models you expect to be pointing to and determine which solution will be most effective for your use case.

Perhaps the solution is something along the lines of using class inheritance from the StateLog model and overriding the object_id field, then allow passing statelog_model='myapp.FooStateLog' or similar to your FSMField.

Did you want to start a PR?

[seocam]

I'm also affected by this issue. Still I'm not sure how to solve it since I'm using FSM with numeric and non-numeric ids.

[destos]

I can probably take a look at a fix today per your suggestion.

[seocam]

The CharField is flexible enough to take UUIDs. Primary Keys as UUIDs are very useful in systems using DB replication.

[ticosax]

I tend to lean towards a similar proposal, maybe with a swappable Model ?
At least we shouldn't force existing users to migrate/change type of object_id field.

[dbinetti]

So glad this repo is getting some love @ticosax Am really hoping that UUID support for PKs can be added, in whatever form; this is really become the norm these days.

[dbinetti]

Happy New Year! What is the status of this issue? Do you need additional feedback on it @ticosax? I'm still using a fork but would love to get back on the main repo.

[ticosax]

@dbinetti Pull requests are welcome. Unfortunately, I don't have myself the need for this use case, so I don't have economical incitement to do it. Suggestions of a suitable approach has been made by @tysonclugg and me. I will help as much as I can once a PR with decent coverage is made.

[dbinetti]

Very well. My fork just runs a migration to CharField; I'm afraid creating swappable models is beyond my skills. I'll just pull from upstream. Thanks!

[riparian-imakedonsky]

Also affected by this issue(we have UUID's as ids). Will copy-paste model to the project with field type changed.
Would be great to just transition to CharField intead, should work seamlessly for anyone.