Closed nick15marketing closed 3 years ago
Thanks!
So ... I merged this and then ran it against a few tables. My opinion is that:
$table->integer('id', 1, 1);
$table->bigInteger('foo', 0, 1);
is not the way Laravel developers would naturally write their migrations, and is less intuitive than:
$table->increments('id');
$table->unsignedBigInteger('foo');
So I've kept some of the parsing code you provided, but updated the output again to use those "natural" migration methods.
…oating point types
This change will allow auto-increment integers that are not unsigned and also adds support for unsigned floating point types. It does this by using the base methods in Blueprint eg integer, tinyInteger etc instead of helper methods integerIncrements etc which assumes unsigned.