{"action":"created","issue":{"url":"https://api.github.com/repos/js-data/js-data/issues/404","repository_url":"https://api.github.com/repos/js-data/js-data","labels_url":"https://api.github.com/repos/js-data/js-data/issues/404/labels{/name}","comments_url":"https://api.github.com/repos/js-data/js-data/issues/404/comments","events_url":"https://api.github.com/repos/js-data/js-data/issues/404/events","html_url":"https://github.com/js-data/js-data/issues/404","id":177218443,"number":404,"title":"Custom Pk field?","user":{"login":"jredd","id":8050852,"avatar_url":"https://avatars.githubusercontent.com/u/8050852?v=3","gravatar_id":"","url":"https://api.github.com/users/jredd","html_url":"https://github.com/jredd","followers_url":"https://api.github.com/users/jredd/followers","following_url":"https://api.github.com/users/jredd/following{/other_user}","gists_url":"https://api.github.com/users/jredd/gists{/gist_id}","starred_url":"https://api.github.com/users/jredd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jredd/subscriptions","organizations_url":"https://api.github.com/users/jredd/orgs","repos_url":"https://api.github.com/users/jredd/repos","events_url":"https://api.github.com/users/jredd/events{/privacy}","received_events_url":"https://api.github.com/users/jredd/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-15T16:04:24Z","updated_at":"2016-09-15T17:00:16Z","closed_at":null,"body":"I have a model that comes in and doesn't have an id field. It's pk is another field all together. I have no control over how the model in the backend is defined and so I have to receive it as is. Is there way to tell the schema that another field is the pk field so I can do things like store.find('someModel', 'uniqueIdentifier') instead of having to do query filters?"},"comment":{"url":"https://api.github.com/repos/js-data/js-data/issues/comments/247387505","html_url":"https://github.com/js-data/js-data/issues/404#issuecomment-247387505","issue_url":"https://api.github.com/repos/js-data/js-data/issues/404","id":247387505,"user":{"login":"jredd","id":8050852,"avatar_url":"https://avatars.githubusercontent.com/u/8050852?v=3","gravatar_id":"","url":"https://api.github.com/users/jredd","html_url":"https://github.com/jredd","followers_url":"https://api.github.com/users/jredd/followers","following_url":"https://api.github.com/users/jredd/following{/other_user}","gists_url":"https://api.github.com/users/jredd/gists{/gist_id}","starred_url":"https://api.github.com/users/jredd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jredd/subscriptions","organizations_url":"https://api.github.com/users/jredd/orgs","repos_url":"https://api.github.com/users/jredd/repos","events_url":"https://api.github.com/users/jredd/events{/privacy}","received_events_url":"https://api.github.com/users/jredd/received_events","type":"User","site_admin":false},"created_at":"2016-09-15T17:00:16Z","updated_at":"2016-09-15T17:00:16Z","body":"Thanks! I actually just found it as I noticed you posted. Wouldn't it be better to define pk's in the schema? You'd be able to keep the definition of the schema contained instead of split apart. It took some digging for me to find this because I was making the wrong assumption about where that would be defined at. Though I can also see the value of defining it on the mapper as well."}}
{"actor":{"display_login":"jredd"}}