fix: add migration to modify chatflowconfig to longtext for mysql #2151
+14
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sickOscar thanks for the fix! However with this PR merged and released, everything is now stored under a local file path instead of a base64 string, hence this fix is no longer needed |
|
having said that, if you still have a lot of nodes and using MySQL, you might still face the issue. See #2159. So we can still proceed with this change |
HenryHengZJ
reviewed
Apr 11, 2024
|
|
||
| export class ExpandChatFlowConfig1712762777471 implements MigrationInterface { | ||
| public async up(queryRunner: QueryRunner): Promise<void> { | ||
| await queryRunner.query(`ALTER TABLE \`chat_flow\` MODIFY \`chatbotConfig\` LONGTEXT;`) |
There was a problem hiding this comment.
is it chatbotConfig that should be changed? isnt it flowData?
There was a problem hiding this comment.
I think that’s may purpose of prevention of exceptions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using big CSV files as document loaders my break mysql chat flow because of the TEXT size of the column and base64 conversion.
Here a migration has been added to change the column type from TEXT to LONGTEXT (4GB of max data)