Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] MySQL - Chat flow JSON data is truncated if more than 65,535 characters #2159

Closed
dev-sareno opened this issue Apr 11, 2024 · 1 comment
Labels
bug Something isn't working in-work Issue in work

Comments

@dev-sareno
Copy link

Describe the bug
When using MySQL database, the flowData column in the chat_flow table only supports up to a maximum of 65,535 characters. Values greater than this length are truncated. The column flowData column stores JSON data and when it's truncated, an error in the browser Uncaught SyntaxError: Unterminated string in JSON at position 65535 is thrown because the data is incomplete.

This issue only happens when using MySQL database, SQLite and Postgres works just fine.

To Reproduce

  1. Use MySQL as a database (DATABASE_TYPE=mysql)
  2. Log in to Flowise and create a new Chatflow
  3. Add nodes as much as you can until the size of the Chatflow JSON reaches more than 65,535 characters
  4. Save Chatflow
  5. Go back to the main page
  6. Open the Chatflow you created in step 3

Expected behavior
It should load the Chatflow/canvas.

Screenshots
image

Setup

  • Installed with Docker
  • Flowise Version 1.6.4 (docker.io/flowiseai/flowise:1.6.4)
  • OS: Linux
  • Browser: Google Chrome

Additional context

A variable-length string. M represents the maximum column length in characters. The range of M is 0 to 65,535. The effective maximum length of a VARCHAR is subject to the maximum row size (65,535 bytes, which is shared among all columns) and the character set used

@HenryHengZJ
Copy link
Contributor

closing as #2908 merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in-work Issue in work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants