Configuration
Database
Last updated
2 years ago.
Solution
I think I've solved my problem; here is what I did:
I have chosen a tricky schema name cascade, please be smarter than me and chose a better one.
I dropped the previous cascade schema first:
drop schema "cascade" cascade;
then I created a new one with proper owner which I think I missed the first time:
create schema "cascade" authorization myusername;
then I tried artisan migrate which ended up with migration complaining about the migration table not being existent. fixed it with running artisan migrate:install and everything worked perfectly afterwards.
Last updated
2 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast