{"action":"created","issue":{"url":"https://api.github.com/repos/django-notifications/django-notifications/issues/125","repository_url":"https://api.github.com/repos/django-notifications/django-notifications","labels_url":"https://api.github.com/repos/django-notifications/django-notifications/issues/125/labels{/name}","comments_url":"https://api.github.com/repos/django-notifications/django-notifications/issues/125/comments","events_url":"https://api.github.com/repos/django-notifications/django-notifications/issues/125/events","html_url":"https://github.com/django-notifications/django-notifications/issues/125","id":142205386,"number":125,"title":"Postgres errors","user":{"login":"savvaoff","id":3892914,"avatar_url":"https://avatars2.githubusercontent.com/u/3892914?v=4","gravatar_id":"","url":"https://api.github.com/users/savvaoff","html_url":"https://github.com/savvaoff","followers_url":"https://api.github.com/users/savvaoff/followers","following_url":"https://api.github.com/users/savvaoff/following{/other_user}","gists_url":"https://api.github.com/users/savvaoff/gists{/gist_id}","starred_url":"https://api.github.com/users/savvaoff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/savvaoff/subscriptions","organizations_url":"https://api.github.com/users/savvaoff/orgs","repos_url":"https://api.github.com/users/savvaoff/repos","events_url":"https://api.github.com/users/savvaoff/events{/privacy}","received_events_url":"https://api.github.com/users/savvaoff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-03-20T20:59:52Z","updated_at":"2018-03-09T09:11:23Z","closed_at":null,"author_association":"NONE","body":"actor_object_id\ntarget_object_id  \naction_object_object_id\n- all the fields have varchar types, that makes it impossible to build queries joining notifications with other tables :(\n\nso, when trying to filter notifications by user id/role get an error in Postgres (cause it's strict about field types):\n\n```\noperator does not exist: character varying = integer\nLINE 1: ... ( \"notifications_notification\".\"actor_object_id\" = \"main_us...\n                                                             ^\nHINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.\n```\n\ncould we set that id fields as int? what was the reason to not to do it?\n"},"comment":{"url":"https://api.github.com/repos/django-notifications/django-notifications/issues/comments/371756082","html_url":"https://github.com/django-notifications/django-notifications/issues/125#issuecomment-371756082","issue_url":"https://api.github.com/repos/django-notifications/django-notifications/issues/125","id":371756082,"user":{"login":"udos","id":141107,"avatar_url":"https://avatars3.githubusercontent.com/u/141107?v=4","gravatar_id":"","url":"https://api.github.com/users/udos","html_url":"https://github.com/udos","followers_url":"https://api.github.com/users/udos/followers","following_url":"https://api.github.com/users/udos/following{/other_user}","gists_url":"https://api.github.com/users/udos/gists{/gist_id}","starred_url":"https://api.github.com/users/udos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/udos/subscriptions","organizations_url":"https://api.github.com/users/udos/orgs","repos_url":"https://api.github.com/users/udos/repos","events_url":"https://api.github.com/users/udos/events{/privacy}","received_events_url":"https://api.github.com/users/udos/received_events","type":"User","site_admin":false},"created_at":"2018-03-09T09:11:23Z","updated_at":"2018-03-09T09:11:23Z","author_association":"NONE","body":"sorry about this. also in my opinion this issue (together with #199) should be closed. basically if maintainers want to keep the functionality compatible to use UUID-type PKs, there might be no other possibility for projects which are using integer PKs as to add explicit type casts when making the queries. see https://stackoverflow.com/a/42152388\r\n\r\napologies for the following (it is not intended in a negative way): then maintainers should decide whether to close the issue or to tag it as a future feature. leaving it open for such a long time (with no activity/communication) is not a good practice..."}}
{"actor":{"display_login":"udos"}}