mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #5638] [bug]: Backend fails to find tables after upgrade to 2025.11.0 – Prisma queries hardcoded schema #2182
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roopepaajanen on GitHub (Dec 1, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5638
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
macOS
Bug Description
After upgrading to Hoppscotch version 2025.11.0 and running the database migration, the backend application fails to start due to missing tables. The migration completes successfully. However, the backend logs show errors indicating that Prisma is attempting to query tables in the
publicschema instead ofhps.Error log:
Migration output:
Environment details:
hpsschemaDATABASE_URLincludes?schema=hpsExpected behavior:
Backend should query tables in the given schema.
Actual behavior:
Backend queries the
publicschema, resulting in table not found errors. If the usage ofpublicschema is required for external databases, I don't think it is documented anywhere (?).Steps to reproduce:
publicschema.Additional info:
This setup worked in previous versions. The issue appeared after the upgrade and migration.
Complete error log from application
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.11.0
@jamesgeorge007 commented on GitHub (Dec 5, 2025):
Closing since this is addressed in the v2025.11.1 release.