title: Getting raw SQL performed by laravel 4 migrations
body: <p>I'm working in an environment where rather than deploying changes directly to the clients servers I have to generate a build tarball with a changelist from an SVN revision and send it over to their web team.</p>
  
  <p>The problem is that I'm not allowed anything fancy, only changes to the site assets and raw queries, this means I can't ask the client to run laravel migrations when I need them to make a change to their staging &amp; live databases (and I don't trust migrations enough for live anyway.) I won't have access to the live database directly either.</p>
  
  <p>So what I want to be able to do is capture the raw SQL when a migration is run, from there I can see exactly what's changing and I can tell the client "here's an SQL file of what needs to change, review it an run it when you apply the update."</p>