Level 28
Does your seeder work if you call it in the console with php artisan db:seed?
1 like
Sep 24, 2019
9
Level 5
"$this->artisan('db:seed');" not seeding properly!
Hello everyone,
I am starting to use Laravels HTTP requests to test our back end API. However, I am running into an issue that I understand but am unable to fix.
The issue:
1) Tests\Unit\WorkspaceListTest::testListWorkspaces
Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1 no such table: main.user (SQL: insert into "collections" (blah blah blah)
First off, the database is not meant to be main and the table is meant to be users and not user! It seems as if the database is not being seeded properly, but I have no idea why :/
The stack trace leads me back to this line of code:
$this->artisan('db:seed');
If anyone could help me understand the underlying problem and possibly help fix this I would be very grateful as I have been stuck on this for quite some time!
Thank you! :)
Level 5
Weird, no it doesn't! Thank you I will check if this works after I have got the seeding to work first!
Level 5
Back again, after clearing up the issue of the database not seeding properly when trying to run "php artisan db:seed" I tried running the test again and I got the exact same issue ??
1) Tests\Unit\WorkspaceListTest::testListWorkspaces
Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1 no such table: main.user (SQL: insert into "collections" (blah blah blah)
I am really confused!
Level 28
That is weird. Do you have changed settings for a testing environment somewhere that might change for example the database name? Like in the phpunit.xml?
Level 5
From what I understand, no. Nothing that changes the database name
Level 13
Can you check your .env file and also config/app.php database name and password?, because this error came from connection to the database.
Level 5
Yes, by the looks of it everything is correct.
Level 5
I have a phpunit.xml that has the environment for the database
Level 3
I faced same issue and I fixed it.
The problem was with the name of my relationship table in migrations.
Before:
$table->foreignId("creator_id")->constrained("user");
After:
$table->foreignId("creator_id")->constrained("users");
Make sure you rerun migrations after this change to have effect
Please or to participate in this conversation.