Missing unique constraint on Jetstream team names (Laravel 9/Jetstream 2.x)

Likely explanation

The default Jetstream 2.x migration for Laravel 9 creates a name column without a UNIQUE index. The package documentation does not mention a unique constraint, and the source code defines the column as a plain string. This omission appears to be an implementation oversight rather than an intentional design choice.

Confirmed facts

• Jetstream provides no built‑in configuration or helper to enforce unique team names.
• Adding a unique index after deployment is safe if no duplicate names exist.
• Application‑level validation alone cannot prevent race conditions under concurrency.

Steps to enforce uniqueness safely

1. Check your database for existing duplicate team names:

   SELECT name, COUNT(*) FROM teams GROUP BY name HAVING COUNT(*) > 1;

   If duplicates are found, resolve them before adding the index.
2. Create a migration that adds a unique index on the name column:

   php artisan make:migration add_unique_index_to_teams_name --table=teams

   Edit the migration to contain:

   Schema::table('teams', function (Blueprint $table) {
           $table->unique('name');
       });

   Run php artisan migrate.
3. Add a unique rule to the CreateTeam request to give early feedback:

   'name' => ['required', 'string', 'max:255', 'unique:teams,name']

4. Wrap team‑creation logic in a database transaction and catch duplicate‑key errors:

   use Illuminate\Support\Facades\DB;
   use Illuminate\Database\QueryException;
   
   public function store(CreateTeam $request)
   {
       try {
           DB::transaction(function () use ($request) {
               $team = $request->user()->ownedTeams()->create([
                   'name' => $request->input('name'),
                   // …other fields
               ]);
           });
       } catch (QueryException $e) {
           if ($e->errorInfo[1] == 1062) { // MySQL duplicate‑entry error code
               return back()->withErrors(['name' => 'The team name has already been taken.']);
           }
           throw $e;
       }
       return redirect()->route('teams.index');
   }

5. Test concurrency in a staging environment by sending two simultaneous requests to create a team with the same name; the second request should receive the validation error.

Missing diagnostic detail

Do you have any existing duplicate team names in your teams table? If duplicates are present, the unique index will fail unless they are resolved first. Let me know the result of the SELECT query above, and I can advise on the safest next step.