#206 bugfix object_id in CalendarRelation

[rodolphopivetta]

Format of object_id in CalendarRelation changed to accept UUID pk, based on documentation

[coveralls]

Coverage remained the same at 65.345% when pulling 30cdd6c on rodolphopivetta:master into a084322 on llazzaro:develop.

[llazzaro]

I think you miss to send the migrations.
Please remember that if required a data migration is also required since a lot of people is using this project.
thanks!

[rodolphopivetta]

Sorry, migrations added :)

[coveralls]

Coverage remained the same at 65.345% when pulling 1c78487 on rodolphopivetta:master into a084322 on llazzaro:develop.

[coveralls]

Coverage remained the same at 65.345% when pulling 1c78487 on rodolphopivetta:master into a084322 on llazzaro:develop.

[coveralls]

Coverage increased (+1.4%) to 66.723% when pulling ab14575 on rodolphopivetta:master into a084322 on llazzaro:develop.

[llazzaro]

I didn't have time to verify with a production database backup. Hope to do it soon

[jdufresne]

@rodolphopivetta Will this change have an affect on performance for integer PK fields?

[jdufresne]

No activity in over a year and there. There are merge conflicts and unanswered review question. I'm closing. If you would like to continue the PR, please answer the above questions and rebase to resolve conflicts. Thanks.

[vegerta]

Can we reopen this pull?

[llazzaro]

@vegerta are you having this bug? can tell us how to reproduce it?

[vegerta]

You can reproduce it, if you make a fresh install and create a model(for expamle: Workers) where you defined the deafult Id field as UUIDField. And when you can try to add some calendar relation you can't save ID value.

[llazzaro]

I will try to review this one.