Relations upload_folders does not exist happening after updating Strapi

[jsanta]

Bug report

Required System information

• Node.js version: 16.15.1
• NPM version: 8.11.0
• Strapi version: 4.3.2
• Database: Postgres 12.11, 14.2
• Operating system: Ubuntu Linux 20.04, MacOS Catalina

Describe the bug

Updated Strapi version from 4.2.0 to 4.3.2, just changed this entries in the package.json file :

"@strapi/plugin-i18n": "4.3.2",
"@strapi/plugin-users-permissions": "4.3.2",
"@strapi/strapi": "4.3.2",

Installed the packages using yarn install, and rebuilt the Strapi admin panel using yarn strapi build
After a while running the server and navigating in the Content Manager started to get this error message:

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
error: select LENGTH(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE("path", $1, $2), $3, $4), $5, $6), $7, $8), $9, $10), $11, $12), $13, $14), $15, $16), $17, $18), $19, $20)) AS depth, COUNT(*) AS occurence from "upload_folders" group by "depth" - relation "upload_folders" does not exist
    at Parser.parseErrorMessage (/opt/queplan/apps/strapi.new/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/opt/queplan/apps/strapi.new/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/opt/queplan/apps/strapi.new/node_modules/pg-protocol/dist/parser.js:39:38)
    at TLSSocket.<anonymous> (/opt/queplan/apps/strapi.new/node_modules/pg-protocol/dist/index.js:11:42)
    at TLSSocket.emit (node:events:527:28)
    at TLSSocket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at TLSSocket.Readable.push (node:internal/streams/readable:228:10)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)

Checked the database tables and the upload_folders table does exist.

Steps to reproduce the behavior

Sorry about not having the precise steps, it happens after a while when navigating inside the Content Manager.

Expected behavior

• No errors are expected due to the database already seem to have all the required relations.
• Double checking the existing database relations before sending an error.
• A more explicit error message in order to be able to look for a workaround.

[petersg83]

Thank you for reporting this issue. Can you tell us how many folders and assets you have in your ML please?

[petersg83]

For info, the code ran can be reproduced by writing this in src/index.js:

  async bootstrap({ strapi }) {
    const m = await strapi.plugin('upload').service('metrics').computeMetrics();
    console.log(m);
  },

[petersg83]

Also, do you see any difference in the names? Some uppercase letters that should be lowercase or else?

[kasonde]

Hi @jsanta quick que: could you confirm that you had media already uploaded in your application before the update?

[jsanta]

Ok some answers.
I did have some media uploaded on my original installation, no more than 10 images.
No folders existed (as folders where introduced after version 4.2).
After placing the suggested code for more info the server won't start at all, showing the exact error I mentioned previously.

[kasonde]

Odd, I can't seem to reproduce it all. I'm gonna change the status of the issue for now but I'm curious to know what's going on. Do you mind updating the issue to add in the exact Postgres version and Linux OS version and info you're using? It could be helpful for us.

[jsanta]

Don't think the Postgres version or the Linux version are so much relevant here, as the same happens on my Mac (Catalina) with Postgres 14.2, where I am developing.
But just in case, Strapi is deployed on an Ubuntu Linux 20.04.03 LTS, connected to a Postgres 12.11 database.
Same yarn.lock and database schema are being used on both development and deployment installations.

[smoothdvd]

@jsanta @kasonde I met this issue also after upgrade from 4.2.3 to 4.3.2.

[2022-08-10 09:38:04.265] error: insert into "files" ("alternative_text", "caption", "created_at", "created_by_id", "ext", "folder_path", "formats", "hash", "height", "mime", "name", "provider", "size", "updated_at", "updated_by_id", "url", "width") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17) returning "id" - column "folder_path" of relation "files" does not exist
error: insert into "files" ("alternative_text", "caption", "created_at", "created_by_id", "ext", "folder_path", "formats", "hash", "height", "mime", "name", "provider", "size", "updated_at", "updated_by_id", "url", "width") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17) returning "id" - column "folder_path" of relation "files" does not exist
    at Parser.parseErrorMessage (/Users/alexgao/Dev/hangzhou-calendar-strapi/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/Users/alexgao/Dev/hangzhou-calendar-strapi/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/Users/alexgao/Dev/hangzhou-calendar-strapi/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/Users/alexgao/Dev/hangzhou-calendar-strapi/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:527:28)
    at Socket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

Because of files table has no folder_path column added. I use PostgreSQL 13.

[petersg83]

Are you able to correctly use the folder feature ? Create folders, put files in them etc.?

[jsanta]

Yes, the folder feature seem to work OK, but nevertheless I'm getting the error message once in a while.