-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 on upgrade to 4.8.0.3 #2480
Comments
Is there a stack trace in your log files? I'd like to know where the problem occurred exactly. |
My log-files: |
I've pushed a fix that you could apply to your own code, if you want to. It involves replacing the code of two functions with the code of the fix. Find this line in your code, and replace everything between Do the same with this function and this replacement. |
I replace code, login in my Firefly III installation, and got the same error message :( ff3-apache2handler-2019-08-25.log A new log file (ff3-cli-2019-08-25) has not been created. In folder only ff3-cli-2019-08-24. |
No worries, we can fix that one as well!
Let me know if it works 👍 |
Now the error message has changed a bit: An unknown error prevented Firefly III from executing the upgrade commands. Sorry. SQLSTATE[HY000]: General error: 1 too many SQL variables (SQL: select * from "transaction_journals" where "id" in (27, 27, 34, [... there are many more id's... ] 3445, 3445) and "transaction_journals"."deleted_at" is null) |
Did you replace both? This is weird because that's all the code there is that's doing large replacements. I'll do some googling but I'm kind of lost, sorry about that. |
Are you using SQLite? |
I replace both (getIdsForBudgets and getIdsForCategories) functions. Yes, I use SQLite DB. |
The fix limits the number of ID's to 50. There may be other commands where this is happening. So keep posting stack traces. I can strongly recommend you to migrate to MySQL or Postgresql though. |
I would gladly switch to MySQL, but there is one problem. I use Firefly III on a shared hosting. And I can’t correctly update my Firefly installation on my server (on the server there is no way to use GIT, Composer, etc.). Now I am doing it simply: copy the database to the local server (where the Composer is), update the Firefly, and copy the updated Firefly along with the database back to the hosting. As soon as the opportunity arises to painlessly upgrade the Firefly with the MySQL database on a shared hosting, I will be happy to switch to MySQL. In the meantime, I have to use SQLite. |
Could you also use the same routine with MySQL? You could use something like Vagrant or Virtualbox to maintain a Linux image with a MySQL database in it. |
But it's tricky, I admit it. |
This is too complicated a procedure. I would not want to make so much effort to update one software. Perhaps there is a way to somehow simplify the process of updating Firefly? At least so: download the full distribution kit of the new version, replace all the files on the server, run the update script. |
Now I try to update from my 4.7.17 to 4.8.1.1. And I get in console new error message:
|
Could you extract the stack trace from the log files? |
Log attached: |
I pushed a fix to the develop branch. If you run across other instances, please open a new ticket. It's easier for me to track :) |
I just upgrade Firefly III from 4.7.17 to 4.8.0.3. I use composer for this. After update, I try to login, Firefly has update database, and I have error-message:
The text was updated successfully, but these errors were encountered: