DB error during API call on backend
See original GitHub issue🐛 Bug Report
- I am including my log files in zip format.
- I have looked for similar issues among all the former issues including closed ones.
What Operating system and version is LibrePhotos running on:
Debian on WSL
What architecture is LibrePhotos running on:
x64
How is LibrePhotos installed:
Docker
If running via Docker or Kubernetes please list version including docker-compose:
3.8
Are you running LibrePhotos on a virtual machine if so please list:
WSL
How is you picture library mounted on the host (or in the virtual machine):
Windows FAT
Description of issue:
API error during DB access from backend while loading after recent update
How can we reproduce it:
I updated the Librephotos version to the latest using docker and restarted my containers. After the backend container came back up, any API call it it throws the error:
django.db.utils.ProgrammingError: column api_photo.image_paths does not exist
LINE 1: SELECT "api_photo"."image_paths", "api_photo"."image_hash", ...
^
HINT: Perhaps you meant to reference the column "api_photo.image_path".
More information included in zipped log including stacks librephotos_error.log
Additional Information:
- Include a ZIP file containing your
logfiles. - Provide pictures or links to videos that clearly demonstrate the issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to return database error from restful service?
The client should not know the server has a problem with some backend. So whether it's the database which causes the issue, should...
Read more >Handle database error for API server
The basic approach is every time a SQL exception occurred, the server will return "500" to client and client will have no idea...
Read more >How To Setup Error Handling For APIs and DB Queries
Errors can pop up and randomly break a user's flow on your app, but there are techniques to make sure you still deliver...
Read more >500 Internal Server Error - Backend Server | Apigee Edge
Symptom. The client application gets an HTTP status code of 500 with the message Internal Server Error as a response for API calls....
Read more >Web API Error Handling: How To Make Debugging Easier
4xx-level errors are client errors. These are errors that the client can solve on their own by changing their request. And then 5xx...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Apparently calling models in migrations the usual way just doesn’t work and django skips the migration without saying why. And it works when you use a new database.
Anyway I pushed a commit which should fix this. The build takes usually half an hour.
Yep its working!