Level 102
What do you mean by randomly?
Feb 16, 2023
14
Level 1
Laravel Notification Table
Hello, everyone, I am working on saving notifications in the notification table which is working fine but the primary key of the tables are being generated randomly instead of auto-incrementing, how can I fix it
{
Schema::create(
'notifications', function (Blueprint $table){
$table->bigIncrements('id');
$table->bigInteger('user_id');
$table->text('type', 30);
$table->text('data');
$table->tinyInteger('is_read');
$table->timestamps();
}
);
}``` This is the migration file of the table
Level 1
if i save one notification the primary key is 1, if i save another now the PK will be 45, the next 35467, the next 466576...
Level 102
@mickiy1 Ok that sounds very very strange. If you use debugbar, can you see the query being written and where from ?
Level 1
@sinnbeck, one use case I am using this for is notifying users when they are assigned to be a project manager what I did was in the controller that is used to assign users as PM, i added this code
$user = User::find($request->project_manager); $user->notify(new ProjectManagerAssignNotification($project));
so it can be saved in the notification table
Level 102
I dont see any reason why that would break the auto increment. It seems that it is setting the ID manually, but I wonder what part of laravel would do that. Debugbar should show that
Level 1
@Sinnbeck any idea on how to get started on debug bar?
Level 102
@mickiy1 Sure. First install it :)
https://packagist.org/packages/barryvdh/laravel-debugbar
Then make a simple route (perhaps just a get route with a view), where you do the dispatch. Then open debugbar on the page (down in the bottom to the left), and select the Queries tab. Here you can see all queries that was run on the page
1 like
Level 42
Please try this for auto-increment in laravel migration
Schema::create( 'notifications', function (Blueprint $table){ $table->increments('id'); } );
Level 102
@saurabhd Any reason that it would work with ->increments() and not ->bigIncrements() ? They are identical, apart from INT vs BIGINT
Level 1
Use UUID for random generate id
1 like
Level 1
just try to use the default $table->id() field
Level 1
Thank you, everyone for the help, i ended up using uuid
Level 102
@mickiy1 just be aware that it isn't good for indexing
1 like
Level 1
I had the same issue! The problem is (I think) the following: Laravels default notifications setup uses a UUID instead of an incrementing integer for the primary key of the Notifications table. You're fine to change that as you did, but you also have to tell Laravel to generate an integer instead of a string. Ohteriwse it probably takes the first integers in the UUID it generated and fill that, causding the random id values. You can do this in your notifications model. Since your model extends DatabaseNotification, you need to override the settings on DatabaseNotification. Set these two values in your Notification model. It fixed the problem for me!
class Notification extends DatabaseNotification
{
protected $keyType = 'integer';
public $incrementing = true;
Please or to participate in this conversation.