Laravel 5.2.14 UUID used for ID Column instead of Illuminate\Database\Schema\Blueprint::increments Unsigned Integer

[mtpultz]

Using this migration and seed, the ID of the inserted row data is a UUID instead of an unsigned integer. I noticed after stubbing through the code for a couple hours trying to find out why an authenticated user couldn't access authenticated routes. The user ID was 8 when there was only 3 users seeded, and it turns out the 8 was just the first digit from the UUID string.

use duxet\Rethinkdb\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateUsersTable extends Migration {

    public function up()
    {
        Schema::create('users', function(Blueprint $table) {
            $table->increments('id');
            ...
        });
    }

    ...
}

Using RethinkDB Blueprint create doesn't implement the Laravel Blueprint API, which includes a version of the increments method.

/**
 * Create a new auto-incrementing integer (4-byte) column on the table.
 *
 * @param  string  $column
 * @return \Illuminate\Support\Fluent
 */
public function increments($column)
{
    return $this->unsignedInteger($column, true);
}

Produces this in RethinkDB's admin panel for this ReQL statement r.db('app').table('users'):

{
"created_at": Fri Feb 12 2016 10:04:22 GMT+00:00 ,
"email": test@test.com, »
"id":  "8bbc1c35-6be5-4b1f-87de-75eba1c459eb" ,
"password":  "$2y$10$2f7QjuBCjEMr3R01ZNlwI.ft8v8FYs8IHRQzPI1lKdojIXtK7b9wO" ,
"role":  "admin" ,
"updated_at": Fri Feb 12 2016 10:04:22 GMT+00:00 ,
"username":  "test"
}

So unless the ID is explicitly set to a unsigned integer it becomes a UUID, which prevents access to routes. The simplest solution might be to have a config for adding UUID to Laravel similar to this implementation or this one.