Why migration integer adds auto_increment and primary key?

@Sinnbeck when I run php artisan migrate I get error:

SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key (SQL: create table `my_table` (`id` bigint unsigned not null auto_increment primary key, `some_col` int not null auto_increment primary key, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

I only did this:

    public function up()
    {
        Schema::create('data', function (Blueprint $table) {
            $table->id();
            $table->integer('some_col', 50);
            $table->timestamps();
         });
    }

@Ligonsker the error says my_table and the migration has data. So wrong migration

@Sinnbeck Oh no, I edited it for this post to make it simpler 😭, it's actually called data

@Ligonsker Remove the 50 from your migration, it's an integer and not a number where you can specify how many digits it may contain.

Here you can read more about datatypes https://tray2.se/posts/database-design-part-2

@Tray2 yep, I confused it with VARCHAR 😅

@MichalOravec correct

public function integer($column, $autoIncrement = false, $unsigned = false)

From some reason I confused it with VARCHAR

@MichalOravec bingo https://laravel.com/api/9.x/Illuminate/Database/Schema/Blueprint.html#method_integer