{"action":"created","issue":{"url":"https://api.github.com/repos/robmorgan/phinx/issues/862","repository_url":"https://api.github.com/repos/robmorgan/phinx","labels_url":"https://api.github.com/repos/robmorgan/phinx/issues/862/labels{/name}","comments_url":"https://api.github.com/repos/robmorgan/phinx/issues/862/comments","events_url":"https://api.github.com/repos/robmorgan/phinx/issues/862/events","html_url":"https://github.com/robmorgan/phinx/issues/862","id":160211645,"number":862,"title":"Need to be able to \"updateData\" when Migrating Existing Tables...","user":{"login":"BallisticPain","id":796026,"avatar_url":"https://avatars.githubusercontent.com/u/796026?v=3","gravatar_id":"","url":"https://api.github.com/users/BallisticPain","html_url":"https://github.com/BallisticPain","followers_url":"https://api.github.com/users/BallisticPain/followers","following_url":"https://api.github.com/users/BallisticPain/following{/other_user}","gists_url":"https://api.github.com/users/BallisticPain/gists{/gist_id}","starred_url":"https://api.github.com/users/BallisticPain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BallisticPain/subscriptions","organizations_url":"https://api.github.com/users/BallisticPain/orgs","repos_url":"https://api.github.com/users/BallisticPain/repos","events_url":"https://api.github.com/users/BallisticPain/events{/privacy}","received_events_url":"https://api.github.com/users/BallisticPain/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-14T15:29:06Z","updated_at":"2016-06-14T18:28:35Z","closed_at":null,"body":"I'm working on a PR for this, but basically we need the ability to migrate data in existing tables and rows. So we need a way to \"update\" a record.\r\n\r\nUnfortunately I had this written on a colleague's system via paired programming, but we lost it when he did a composer update ... DOH!\r\n\r\nAlso @robmorgan, is this something you would consider if I provide all the necessary pieces in the PR? I'm going to submit regardless, just wanted to know.\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/robmorgan/phinx/issues/comments/225972954","html_url":"https://github.com/robmorgan/phinx/issues/862#issuecomment-225972954","issue_url":"https://api.github.com/repos/robmorgan/phinx/issues/862","id":225972954,"user":{"login":"BallisticPain","id":796026,"avatar_url":"https://avatars.githubusercontent.com/u/796026?v=3","gravatar_id":"","url":"https://api.github.com/users/BallisticPain","html_url":"https://github.com/BallisticPain","followers_url":"https://api.github.com/users/BallisticPain/followers","following_url":"https://api.github.com/users/BallisticPain/following{/other_user}","gists_url":"https://api.github.com/users/BallisticPain/gists{/gist_id}","starred_url":"https://api.github.com/users/BallisticPain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BallisticPain/subscriptions","organizations_url":"https://api.github.com/users/BallisticPain/orgs","repos_url":"https://api.github.com/users/BallisticPain/repos","events_url":"https://api.github.com/users/BallisticPain/events{/privacy}","received_events_url":"https://api.github.com/users/BallisticPain/received_events","type":"User","site_admin":false},"created_at":"2016-06-14T18:28:35Z","updated_at":"2016-06-14T18:28:35Z","body":"@rquadling I appreciate you sharing that, but I'm updating 144 thousand rows of data with many columns of data. I wanted to be able to use a method similar to the setData. We are morphing a legacy users table, and we want this managed by the migration. Thankfully the down is simple and it drops the columns. However, the up requires data to be input into each column that is unable to accept a `null`.\r\n\r\nWe actually don't yet have services to handle changing this data as we are starting by adding the columns."}}
{"actor":{"display_login":"BallisticPain"}}