error: "Field is already defined on model" when field has same name as table about electric

[kevin-dp]

Hi @barbalex,
I did not find the time to look deep into this issue, but from your description this looks like a Prisma issue.
Your files table defines foreign keys to accounts, projects, actions, etc. Therefore, Prisma will define a relation field from that other table to files. If there is only a single relation from that other table to files, i believe it will use the name of that other table (i.e. files) as the name of the relation field. Now, in your case, this leads to a name clash because the table actions already has a column named files.

If you open .electric_migrations_tmp_a8tY7C/prisma/schema.prisma you will probably see that the generate Prisma schema has two fields named files on the accounts model, one that represents the boolean files column you defined in your Postgres schema, and one that represents the reverse FK relation with the files table.

I'd suggest renaming either the files table or the files column on the action table to avoid this name clash.

[barbalex]

@kevin-dp

You are 100% right, it seems. Thanks a lot!

I now renamed the fields. The shema builds so I suppose that was correct.
I do get a different issue now though: #750