{"action":"closed","issue":{"url":"https://api.github.com/repos/metabase/metabase/issues/2641","repository_url":"https://api.github.com/repos/metabase/metabase","labels_url":"https://api.github.com/repos/metabase/metabase/issues/2641/labels{/name}","comments_url":"https://api.github.com/repos/metabase/metabase/issues/2641/comments","events_url":"https://api.github.com/repos/metabase/metabase/issues/2641/events","html_url":"https://github.com/metabase/metabase/issues/2641","id":156186257,"number":2641,"title":"Can't filter by binary values in MySQL","user":{"login":"arabold","id":1548229,"avatar_url":"https://avatars.githubusercontent.com/u/1548229?v=3","gravatar_id":"","url":"https://api.github.com/users/arabold","html_url":"https://github.com/arabold","followers_url":"https://api.github.com/users/arabold/followers","following_url":"https://api.github.com/users/arabold/following{/other_user}","gists_url":"https://api.github.com/users/arabold/gists{/gist_id}","starred_url":"https://api.github.com/users/arabold/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arabold/subscriptions","organizations_url":"https://api.github.com/users/arabold/orgs","repos_url":"https://api.github.com/users/arabold/repos","events_url":"https://api.github.com/users/arabold/events{/privacy}","received_events_url":"https://api.github.com/users/arabold/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/metabase/metabase/labels/Database/MySQL","name":"Database/MySQL","color":"782E53"},{"url":"https://api.github.com/repos/metabase/metabase/labels/Limitation","name":"Limitation","color":"CC333F"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2016-05-23T01:46:13Z","updated_at":"2016-05-24T17:03:06Z","closed_at":"2016-05-24T17:03:06Z","body":"We're using `BINARY` data types for our primary keys and foreign key relationships. Basically those are UUIDs but hexed into their binary form (this happens internally in our framework using MySQL's `UNHEX()` function). Unfortunately `BINARY` columns that doesn't seem to be well supported in Metabase. The values are actually cut off after 8 characters. Here's how that look like in Metabase:\r\n![image](https://cloud.githubusercontent.com/assets/1548229/15458238/1e35254c-204c-11e6-9650-f149411660da.png)\r\n\r\nThe first value for example should be `0x00011717F79511E5B7CD12E00F998A0F` instead of just `0x00011717`. Due to this issue other features of Metabase aren't working either. I cannot navigate between foreign key relationships, I cannot even filter for a specific ID - neither querying for `0x00011717` nor for the full `0x00011717F79511E5B7CD12E00F998A0F` yields any results.\r\n\r\nI'm using Metabase 0.17.1 with a MySQL 5.6 (AWS Aurora) database.\r\n"}}
{"actor":{"display_login":"camsaul"}}