{"action":"reopened","issue":{"url":"https://api.github.com/repos/dmfay/massive-js/issues/474","repository_url":"https://api.github.com/repos/dmfay/massive-js","labels_url":"https://api.github.com/repos/dmfay/massive-js/issues/474/labels{/name}","comments_url":"https://api.github.com/repos/dmfay/massive-js/issues/474/comments","events_url":"https://api.github.com/repos/dmfay/massive-js/issues/474/events","html_url":"https://github.com/dmfay/massive-js/issues/474","id":259296433,"number":474,"title":"New JSON traversal doesn't work in order option","user":{"login":"cjevning","id":4167923,"avatar_url":"https://avatars0.githubusercontent.com/u/4167923?v=4","gravatar_id":"","url":"https://api.github.com/users/cjevning","html_url":"https://github.com/cjevning","followers_url":"https://api.github.com/users/cjevning/followers","following_url":"https://api.github.com/users/cjevning/following{/other_user}","gists_url":"https://api.github.com/users/cjevning/gists{/gist_id}","starred_url":"https://api.github.com/users/cjevning/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cjevning/subscriptions","organizations_url":"https://api.github.com/users/cjevning/orgs","repos_url":"https://api.github.com/users/cjevning/repos","events_url":"https://api.github.com/users/cjevning/events{/privacy}","received_events_url":"https://api.github.com/users/cjevning/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-09-20T20:45:51Z","updated_at":"2017-09-21T00:08:31Z","closed_at":null,"author_association":"NONE","body":"The new JSON traversal methods work well in the criteria object, however they don't seem to work when used in the query options, for example I have a JSONB column `timing` and can select `timing.claim` but if I wanted to order by it, using `timing.claim` results in a `42P01` error from postgres, while using the standard PG form (`timing->>'claim'`) works as expected.\r\n```\r\norder: [{ field: \"timing.claim\", direction: 'desc' }]    // doesn't work, 42P01\r\norder: [{ field: \"timing->>'claim'\", direction: 'desc' }]    // works fine\r\n```\r\nNot sure if this is a bug or if this is expected behavior, although if it's the intended behavior it may be worth making that more clear in the documentation."}}
{"actor":{"display_login":"dmfay"}}