Upon running a comparison of the two databases, it correctly identifies the new `active` column and shows it as:

`active` tinyint(4) NOT NULL DEFAULT 1,

Upon running the deployment I get a "No value specified for a NOT NULL column". Here I have to manually change the dropdown to "Specify custom value" and change the value to 1.

In a simple example like this, that's not too much of a hassle but when you're using this for larger deployments, this can become quite annoying if there are lots of new NOT NULL columns with DEFAULT values specified.