{"action":"closed","issue":{"url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2184","labels_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2184/labels{/name}","comments_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2184/comments","events_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2184/events","html_url":"https://github.com/sequelpro/sequelpro/issues/2184","id":97049078,"number":2184,"title":"Using SequelPro corrupts Mysql bin log","user":{"login":"bbreukelen","id":1590898,"avatar_url":"https://avatars.githubusercontent.com/u/1590898?v=3","gravatar_id":"","url":"https://api.github.com/users/bbreukelen","html_url":"https://github.com/bbreukelen","followers_url":"https://api.github.com/users/bbreukelen/followers","following_url":"https://api.github.com/users/bbreukelen/following{/other_user}","gists_url":"https://api.github.com/users/bbreukelen/gists{/gist_id}","starred_url":"https://api.github.com/users/bbreukelen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bbreukelen/subscriptions","organizations_url":"https://api.github.com/users/bbreukelen/orgs","repos_url":"https://api.github.com/users/bbreukelen/repos","events_url":"https://api.github.com/users/bbreukelen/events{/privacy}","received_events_url":"https://api.github.com/users/bbreukelen/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/sequelpro/sequelpro/labels/Bug","name":"Bug","color":"fc2929"},{"url":"https://api.github.com/repos/sequelpro/sequelpro/labels/Priority-High","name":"Priority-High","color":"e11d21"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-07-24T13:08:33Z","updated_at":"2015-07-29T14:53:21Z","closed_at":"2015-07-29T14:53:21Z","body":"On my server, using sequelPro to make any transactions in a mysql database makes the mysql binlog unusable.\r\n\r\nSee screenshot:\r\n![screen shot 2015-07-24 at 15 05 44](https://cloud.githubusercontent.com/assets/1590898/8874907/80d18540-3215-11e5-94d2-de43a24b0cf3.png)\r\n\r\nThe insert done by SequelPro generates a weird character behind the statement that mysql does not like. Mysql's behaviour during an import of this SQL file is unpredictable. It will not always throw an error but the row will not be inserted.\r\n\r\nAll database char% variables are set to utf-8 and so is the encoding setting on sequelPro.\r\n\r\nAny idea how to fix this issue? A single update/insert/delete/alter from my client makes the entire binlog unusable.\r\n\r\nThanks"}}