Laravel migrate creating table with more than one primary key

Question

I issued the command:

php artisan generate:scaffold order --fields="customer_id:integer(11), order_date:date, notes:text”

When it gets to migrate, it ends with the error:

General error: 1 table "orders" has more than one primary key (SQL: create table "orders" ("id" integer not null primary key autoincrement, "customer_id" integer not null primary key autoincrement, "order_date" date not null, "notes" text not null))

There is a Customer model and corresponding table that I am trying to reference with customer_id in the schema. However, it shouldn't be the primary key for the orders table.

Here is the up() code that is preventing migration from running:

    Schema::create('orders', function(Blueprint $table)
    {
        $table->increments('id');
        $table->integer('customer_id', 11);
        $table->date('order_date');
        $table->text('notes');
        $table->timestamps();
    });

How do I get this to work?

the generate:scaffold commands is generating the sql with 2 primary keys ( customer_id and id ) . Are you sure that's the up migrate that is not working ? Do you currently have a orders table ? — Paul Bele
– Paul Bele, Commented Apr 16, 2014 at 5:06

Daan · Accepted Answer · 2016-08-18 16:00:45Z

7

The problem is that you use the function ->integer() with a second param. According to the docs the second parameter expects a boolean to set autoincrement or not: bool $autoIncrement = false).

Try this:

Schema::create('orders', function(Blueprint $table)
    {
        $table->increments('id');
        $table->integer('customer_id');
        $table->date('order_date');
        $table->text('notes');
        $table->timestamps();
    });

answered Aug 18, 2016 at 16:00

Daan

7,9615 gold badges47 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

dmmd Over a year ago

I think this should be the right answer, as it clearly was the issue here.

Community · Accepted Answer · 2017-05-23 12:08:38Z

1

A possible problem might be :

from here

Root of problem is : column with foreign key must be same type as that key. And you have different types: INT/UNSIGNED INT

The documentation on Laravel mentions this also : Note: When creating a foreign key that references an incrementing integer, remember to always make the foreign key column unsigned.

edited May 23, 2017 at 12:08

CommunityBot

11 silver badge

answered Apr 16, 2014 at 5:12

Paul Bele

1,5341 gold badge11 silver badges12 bronze badges

Collectives™ on Stack Overflow

Laravel migrate creating table with more than one primary key

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related