Fixed boolean and integer type attributes for MySQL by bilaliqbalr · Pull Request #1786 · evolution-foundation/evolution-api · GitHub

🐞 Describe the bug

When running the container and executing Prisma commands for MySQL, Prisma throws schema validation errors due to incorrect native type usage in mysql-schema.prisma. The current schema uses PostgreSQL-native types (@db.Integer, @db.Boolean, etc.), which are not valid for MySQL.

🧪 Steps to reproduce

Pull the latest Evolution API Docker image (2.3.1)
Ensure .env is correctly set for a MySQL database
Run:

Which version of the API are you using?

latest

What is your environment?

Linux

Other environment specifications

No response

If applicable, paste the log output

Prisma schema loaded from prisma/mysql-schema.prisma
Error: Prisma schema validation - (get-dmmf wasm)
Error code: P1012
error: Native type Boolean is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:650
   | 
649 |   id              String           @id @default(cuid())
650 |   enabled         Boolean          @default(true) @db.Boolean
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:657
   | 
656 |   keywordFinish   String?          @db.VarChar(100)
657 |   delayMessage    Int?             @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:662
   | 
661 |   keepOpen        Boolean?         @default(false)
662 |   debounceTime    Int?             @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:665
   | 
664 |   splitMessages   Boolean?         @default(false)
665 |   timePerChar     Int?             @default(50) @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:680
   | 
679 |   keywordFinish   String?   @db.VarChar(100)
680 |   delayMessage    Int?      @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:685
   | 
684 |   keepOpen        Boolean?  @default(false)
685 |   debounceTime    Int?      @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:688
   | 
687 |   splitMessages   Boolean?  @default(false)
688 |   timePerChar     Int?      @default(50) @db.Integer
   | 
error: Native type Boolean is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:699
   | 
698 |   id              String           @id @default(cuid())
699 |   enabled         Boolean          @default(true) @db.Boolean
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:705
   | 
704 |   keywordFinish   String?          @db.VarChar(100)
705 |   delayMessage    Int?             @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:710
   | 
709 |   keepOpen        Boolean?         @default(false)
710 |   debounceTime    Int?             @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:713
   | 
712 |   splitMessages   Boolean?         @default(false)
713 |   timePerChar     Int?             @default(50) @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:728
   | 
727 |   keywordFinish   String?   @db.VarChar(100)
728 |   delayMessage    Int?      @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:733
   | 
732 |   keepOpen        Boolean?  @default(false)
733 |   debounceTime    Int?      @db.Integer
   | 
error: Native type Integer is not supported for mysql connector.
  -->  prisma/mysql-schema.prisma:736
   | 
735 |   splitMessages   Boolean?  @default(false)
736 |   timePerChar     Int?      @default(50) @db.Integer
   | 
error: Error validating field `Instance` in model `N8nSetting`: The relation field `Instance` on model `N8nSetting` is missing an opposite relation field on the model `Instance`. Either run `prisma format` or add it manually.
  -->  prisma/mysql-schema.prisma:693
   | 
692 |   n8nIdFallback   String?   @db.VarChar(100)
693 |   Instance        Instance  @relation(fields: [instanceId], references: [id], onDelete: Cascade)
694 |   instanceId      String    @unique
   | 
error: Error validating field `Instance` in model `Evoai`: The relation field `Instance` on model `Evoai` is missing an opposite relation field on the model `Instance`. Either run `prisma format` or add it manually.
  -->  prisma/mysql-schema.prisma:719
   | 
718 |   updatedAt       DateTime         @updatedAt @db.Timestamp
719 |   Instance        Instance         @relation(fields: [instanceId], references: [id], onDelete: Cascade)
720 |   instanceId      String
   | 
error: Error validating field `Instance` in model `EvoaiSetting`: The relation field `Instance` on model `EvoaiSetting` is missing an opposite relation field on the model `Instance`. Either run `prisma format` or add it manually.
  -->  prisma/mysql-schema.prisma:741
   | 
740 |   evoaiIdFallback String?   @db.VarChar(100)
741 |   Instance        Instance  @relation(fields: [instanceId], references: [id], onDelete: Cascade)
742 |   instanceId      String    @unique
   | 

Validation Error Count: 17
[Context: getDmmf]

Prisma CLI Version : 6.11.1
Error executing command: npx prisma generate --schema ./prisma/mysql-schema.prisma
Prisma generate failed

Summary by Sourcery

Fix Prisma schema validation errors for MySQL by correcting unsupported native type annotations on Boolean and Int fields and restoring missing inverse relations on the Instance model.

Bug Fixes:

Remove unsupported @db.Boolean annotations from Boolean fields in the MySQL Prisma schema
Remove unsupported @db.Integer annotations from Int fields in the MySQL Prisma schema
Add missing opposite relation fields for Instance on N8nSetting, Evoai, and EvoaiSetting models

Reviewer's Guide

This PR fixes schema validation errors by replacing unsupported PostgreSQL native type annotations in the MySQL Prisma schema with correct MySQL types or defaults, and adds the missing opposite relation fields on the Instance model to complete bidirectional relations.

File-Level Changes

Change	Details	Files
Correct native type annotations for boolean fields	Removed all @db.Boolean annotations Replaced unsupported boolean native types with @db.TinyInt(1) or default mapping	prisma/mysql-schema.prisma
Correct native type annotations for integer fields	Removed all @db.Integer annotations Replaced unsupported integer native types with default Int mapping	prisma/mysql-schema.prisma
Add missing inverse relation fields on Instance model	Defined relation fields for N8nSetting, Evoai, and EvoaiSetting on Instance Ensured each relation uses @relation with correct reference and onDelete behavior	prisma/mysql-schema.prisma

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

Hey @bilaliqbalr - I've reviewed your changes and they look great!

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

DavidsonGomes and others added 2 commits July 29, 2025 09:20

Merge branch 'release/1.3.1'

9cdb897

Fixed boolean and integer type attributes

095e435

sourcery-ai Bot reviewed Jul 31, 2025

View reviewed changes

DavidsonGomes changed the base branch from main to develop August 4, 2025 21:51

DavidsonGomes merged commit dab66fc into evolution-foundation:develop Aug 4, 2025
1 check passed

Fixed boolean and integer type attributes for MySQL by bilaliqbalr · Pull Request #1786 · evolution-foundation/evolution-api · GitHub

Uh oh!

Fixed boolean and integer type attributes for MySQL - #1786

Fixed boolean and integer type attributes for MySQL#1786
DavidsonGomes merged 2 commits into
evolution-foundation:developfrom
bilaliqbalr:patch-1

bilaliqbalr commented Jul 31, 2025 •
edited by sourcery-ai Bot
Loading

Uh oh!

Uh oh!

sourcery-ai Bot commented Jul 31, 2025 •
edited
Loading

Uh oh!

Uh oh!

sourcery-ai Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Fixed boolean and integer type attributes for MySQL by bilaliqbalr · Pull Request #1786 · evolution-foundation/evolution-api · GitHub

Uh oh!

Fixed boolean and integer type attributes for MySQL - #1786

Fixed boolean and integer type attributes for MySQL#1786DavidsonGomes merged 2 commits intoevolution-foundation:developevolution-foundation/evolution-api:developfrom bilaliqbalr:patch-1bilaliqbalr/evolution-api:patch-1Copy head branch name to clipboard

Conversation

bilaliqbalr commented Jul 31, 2025 • edited by sourcery-ai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🐞 Describe the bug

🧪 Steps to reproduce

Which version of the API are you using?

What is your environment?

Other environment specifications

If applicable, paste the log output

Summary by Sourcery

Uh oh!

sourcery-ai Bot commented Jul 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Fixed boolean and integer type attributes for MySQL#1786
DavidsonGomes merged 2 commits into
evolution-foundation:developfrom
bilaliqbalr:patch-1

bilaliqbalr commented Jul 31, 2025 •
edited by sourcery-ai Bot
Loading

sourcery-ai Bot commented Jul 31, 2025 •
edited
Loading