Migrate strapi_permission (v3) into admin_permissions (v4) - column "fields" of relation "admin_permissions" does not exist

[mannp]

Bug report

Taken 8hrs to get this far :-/

Required System information

- Node.js version: v16.15.0
- Source Strapi version: 3
- Target Strapi version: 4
- Source Database: postgres
- Target Database: postgres
- Operating system: nixos
- Which script are you running: v3-sql-v4-sql

Describe the bug

Migration failure

error: insert into "admin_permissions" ("action", "conditions", "created_at", "fields", "id", "properties", "subject", "updated_at") values ($1, $2, $3, $4, $5, $6, $7, $8), ($9, $10, $11, $12, $13, $14, $15, $16), ($17, $18, $19, $20, $21, $22, $23, $24), ($25, $26, $27, $28, $29, $30, $31, $32), ($33, $34, $35, $36, $37, $38, $39, $40), ($41, $42, $43, $44, $45, $46, $47, $48), ($49, $50, $51, $52, $53, $54, $55, $56), ($57, $58, $59, $60, $61, $62, $63, $64), ($65, $66, $67, $68, $69, $70, $71, $72), ($73, $74, $75, $76, $77, $78, $79, $80), ($81, $82, $83, $84, $85, $86, $87, $88), ($89, $90, $91, $92, $93, $94, $95, $96), ($97, $98, $99, $100, $101, $102, $103, $104), ($105, $106, $107, $108, $109, $110, $111, $112), ($113, $114, $115, $116, $117, $118, $119, $120), ($121, $122, $123, $124, $125, $126, $127, $128), ($129, $130, $131, $132, $133, $134, $135, $136), ......... - column "fields" of relation "admin_permissions" does not exist

Steps to reproduce the behaviour

Follow v3-sql-v4-sql guide and migrate.

Expected behaviour

A smooth transition from Strapi V3 to V4

[LucaNerlich]

You will need to provide some rough idea of your data schema, otherwise its impossible to help.
A barebones v3 -> v4 does not break with this error.

[mannp]

You will need to provide some rough idea of your data schema, otherwise its impossible to help. A barebones v3 -> v4 does not break with this error.

Perhaps you can help me with what files / api I can share to give you that information?

Is the migration a dumb copy of data, or does it create tables when needed?

[derrickmehaffy]

@mannp it does not create the tables for you. As the instructions suggest you need to initialize your v4 database before you run the script. You init the DB by starting the v4 App which auto creates the tables and columns.

[derrickmehaffy]

We need more information on the model structure, ideally if your project code is open source could you link to your v3/v4 branches?

[mannp]

@mannp it does not create the tables for you. As the instructions suggest you need to initialize your v4 database before you run the script. You init the DB by starting the v4 App which auto creates the tables and columns.

Thanks, @derrickmehaffy, I have already, done this, but the table in v3 does not exist in v4 so init the v4 db would not help, would it?

[mannp]

We need more information on the model structure, ideally if your project code is open source could you link to your v3/v4 branches?

It is not accessible, but I can copy and paste what is needed...where would I look for the model structure relating to 'column "fields" of relation "admin_permissions" does not exist'?

More simply, how do I show the model structure to help you, help me?

[LucaNerlich]

you could for example use a tool to visualise your v3 database schema. For example Jetbrains DataGrip allows you to "right click" a schema/database -> generate diagram.

[derrickmehaffy]

@mannp it does not create the tables for you. As the instructions suggest you need to initialize your v4 database before you run the script. You init the DB by starting the v4 App which auto creates the tables and columns.

Thanks, @derrickmehaffy, I have already, done this, but the table in v3 does not exist in v4 so init the v4 db would not help, would it?

I should clarify it won't create any of the new v4 tables for you as they should already exist. The script takes the old data/format in v3, converts it to the various v4 formats, and writes them into the new v4 table structure generated by starting the app.

You need two different databases, one for v3 and one for v4.

[mannp]

@mannp it does not create the tables for you. As the instructions suggest you need to initialize your v4 database before you run the script. You init the DB by starting the v4 App which auto creates the tables and columns.

Thanks, @derrickmehaffy, I have already, done this, but the table in v3 does not exist in v4 so init the v4 db would not help, would it?

I should clarify it won't create any of the new v4 tables for you as they should already exist. The script takes the old data/format in v3, converts it to the various v4 formats, and writes them into the new v4 table structure generated by starting the app.

You need two different databases, one for v3 and one for v4.

I have two databases v3 and v4 as per the guide.

Unfortunately, it doesn't do this;

The script takes the old data/format in v3, converts it to the various v4 formats, and writes them into the new v4 table structure

If the v4 structure is not identical to the v3 then it does not work.

[derrickmehaffy]

Is your issue the same as #5 ?

[mannp]

Is your issue the same as #5 ?

I will check tomorrow, after checking this out -> https://www.npmjs.com/package/strapi-plugin-entity-relationship-chart/v/3.1.0

It might show the model structure....

Edit: Quick glance, and it does indeed look similar for sure...

[tonoli]

I have exactly the same issue. When I start a v4 project the table admin_permissions does not have the column "fields" created so I run into the same issue:

Migrating 305 items from strapi_permission to admin_permissions
strapi_permission batch #1
(node:15999) UnhandledPromiseRejectionWarning: error: insert into "admin_permissions" ("action", "conditions", "created_at", "fields", "id", "properties", "subject", "updated_at") values ($1, $2, $3, $4, $5, $6