[1.23.X] The table `public.Group` does not exist in the current database

[dpapagiannis]

Since updating to version 1.23 from 1.22, I have been having the following errors on the browser's console when I access the application on the /groups page:

[
  {
    "error": {
      "json": {
        "message": "\nInvalid `prisma.group.findMany()` invocation:\n\n\nThe table `public.Group` does not exist in the current database.",
        "code": -32603,
        "data": {
          "code": "INTERNAL_SERVER_ERROR",
          "httpStatus": 500,
          "path": "groups.list"
        }
      }
    }
  }
]

The application's backend logs are below:

spliit  | ⨯ Error [PrismaClientKnownRequestError]:
spliit  | Invalid `prisma.group.findUnique()` invocation:
spliit  |
spliit  |
spliit  | The table `public.Group` does not exist in the current database.
spliit  |     at async Module.h [as generateMetadata] (.next/server/chunks/ssr/[root-of-the-server]__09c-nik._.js:1:1787) {
spliit  |   code: 'P2021',
spliit  |   meta: {
spliit  |     modelName: 'Group',
spliit  |     driverAdapterError: Error [DriverAdapterError]: TableDoesNotExist
spliit  |         at F.onError (.next/server/chunks/ssr/_17rru9p._.js:1:8309)
spliit  |         at F.performIO (.next/server/chunks/ssr/_17rru9p._.js:1:8250)
spliit  |         at async F.queryRaw (.next/server/chunks/ssr/_17rru9p._.js:1:4838) {
spliit  |       [cause]: [Object]
spliit  |     }
spliit  |   },
spliit  |   clientVersion: '7.9.1',
spliit  |   digest: '2096996732'
spliit  | }

Downgrading to 1.22 makes the error go away and the application works correctly, displaying the groups that were previously stored.

The table does exist in the database of course, i'm just not sure why 1.23 does not find it.

I'm using postgres 18.

[4ndyZ]

I experienced the exact same problem. I run the same setup with PostgreSQL 18.

Downgrade to Container Image version 1.22.0 solved the problem for me too.

---

I found out that there was a change in the database handling for postgres. (see 0ec55d6).

@prisma/client used the postgres database as default.

The new used @prisma/adapter-pg with @/generated/prisma/client does no longer use the postgres database as default. It does not define its own default database instead it inherits pg defaults (in a normal setup the users database).

Therefore the simple "fix" is to use explicitly set the database in the database url by appending /postgres.

POSTGRES_PRISMA_URL=postgresql://<Username>:<Password>@<Host>:<Port>/postgres
POSTGRES_URL_NON_POOLING=postgresql://<Username>:<Password>@<Host>:<Port>/postgres

This problem only occurs then the database was not set in the database url beforehand.

---

Side note, another problem can be that the @prisma/adapter-pg used in

spliit/src/lib/prisma.ts

Lines 8 to 11 in 0ec55d6

	function createPrismaClient() {
	const adapter = new PrismaPg({
	connectionString: process.env['POSTGRES_PRISMA_URL'],
	})

does no longer support other schema in the database URL (see: prisma/orm#28128 ).

[dpapagiannis]

Therefore the simple "fix" is to use explicitly set the database in the database url by appending /postgres.

Good catch! This indeed seems like a workaround, and there should definitely be some warning to the users who want to upgrade. A unit test should also probably be in place for that.