{"action":"created","issue":{"url":"https://api.github.com/repos/cakephp/cakephp/issues/7013","labels_url":"https://api.github.com/repos/cakephp/cakephp/issues/7013/labels{/name}","comments_url":"https://api.github.com/repos/cakephp/cakephp/issues/7013/comments","events_url":"https://api.github.com/repos/cakephp/cakephp/issues/7013/events","html_url":"https://github.com/cakephp/cakephp/issues/7013","id":94955256,"number":7013,"title":"Support for treating BINARY(36) in CakePHP 3.x","user":{"login":"adduc","id":44527,"avatar_url":"https://avatars.githubusercontent.com/u/44527?v=3","gravatar_id":"","url":"https://api.github.com/users/adduc","html_url":"https://github.com/adduc","followers_url":"https://api.github.com/users/adduc/followers","following_url":"https://api.github.com/users/adduc/following{/other_user}","gists_url":"https://api.github.com/users/adduc/gists{/gist_id}","starred_url":"https://api.github.com/users/adduc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adduc/subscriptions","organizations_url":"https://api.github.com/users/adduc/orgs","repos_url":"https://api.github.com/users/adduc/repos","events_url":"https://api.github.com/users/adduc/events{/privacy}","received_events_url":"https://api.github.com/users/adduc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-14T14:20:53Z","updated_at":"2015-07-14T16:31:39Z","closed_at":null,"body":"Hello,\r\n\r\nAs I understand it, CakePHP 1.x and 2.x had support for treating both CHAR(36) and BINARY(36) database fields as UUID. While CakePHP 3.x supports treating CHAR(36) as UUID, it does not appear to offer the same behavior for BINARY(36) fields. Could this feature be added back in a future 3.x release? I would be willing to develop it."},"comment":{"url":"https://api.github.com/repos/cakephp/cakephp/issues/comments/121297928","html_url":"https://github.com/cakephp/cakephp/issues/7013#issuecomment-121297928","issue_url":"https://api.github.com/repos/cakephp/cakephp/issues/7013","id":121297928,"user":{"login":"markstory","id":24086,"avatar_url":"https://avatars.githubusercontent.com/u/24086?v=3","gravatar_id":"","url":"https://api.github.com/users/markstory","html_url":"https://github.com/markstory","followers_url":"https://api.github.com/users/markstory/followers","following_url":"https://api.github.com/users/markstory/following{/other_user}","gists_url":"https://api.github.com/users/markstory/gists{/gist_id}","starred_url":"https://api.github.com/users/markstory/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markstory/subscriptions","organizations_url":"https://api.github.com/users/markstory/orgs","repos_url":"https://api.github.com/users/markstory/repos","events_url":"https://api.github.com/users/markstory/events{/privacy}","received_events_url":"https://api.github.com/users/markstory/received_events","type":"User","site_admin":false},"created_at":"2015-07-14T16:31:39Z","updated_at":"2015-07-14T16:31:39Z","body":"I'm assuming you're using mysql? I don't think we ever supported binary(36) in sqlserver or postgres.\r\n\r\nIn addition to handling the column reflection, we'd also need to solve how this uuid type is different from the string one. Right now all the uuid implementations use ascii encoded data. I don't think that is going to be feasible if we also have to handle binary blobs."}}