-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in Laravel 8 migration problem, There is no active transaction #532
Comments
Hello
Hello, your have found a solved to the problem? |
@HDsouls not yet, i think this package is not available for php 8 or laravel 8 |
You can 'fix' this by updating some code in PragmaRX\Support\Migration The issue is with PHP8 and PDO transaction stuff. The original code of the 'executeInTransaction' function needs to be amended. The original code is:
Change the last bit to:
It works for me but I haven't tested it more broadly. |
Thanks for the tip @ingoldsby - Have you had any side affects from this in the last 15 days? Or noticed any other issues abroad |
I'm not sure if it was related or not, but I had some session_start() issues when I pushed it to AWS from local computer. So I took it off for now until I get time to investigate more. |
Check if your php.ini file has php_pdo extension enabled. I am trying this on Laravel 8.44 and it migrated the migration files. I got the blade files through git checkout and opened Stats route which now only gives me Datatables error. PS I did not follow @ingoldsby 's advice |
Thank you it worked, rather than overwriting the packages I duplicated PragmaRX\Support\Migration locally as a util, applied the changes you suggested, and imported my util in the all the migrations. |
Any negative impact with this popup error? @rohanshukla9 |
had the same error. Found a work around by editing by editing the commit function. I reduced the transaction count to zero. Was able to seed without error, rolled back the code after I was through. Hope it helps someone. public function commit()
|
This error can be caused by different things, but ultimately a transaction being committed prematurely. For me it was the because my base |
The solution from @bradietilley worked for me. After doing a little research I found out that |
after installing this package and define settings into
app/config.php
and publishing configuration, when i try to run this command:i get error after this part of
readme
install documentError:
I'm using
Docker
asLaraDock
and this is mydatabase
file content:The text was updated successfully, but these errors were encountered: