-
-
Notifications
You must be signed in to change notification settings - Fork 979
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
Best practice to store the created diagram #119
Comments
If you want to store the long nodes in the SQL database I prefer to store it in JSON format. I used in my case 3800 Nodes converted into the JSON string and stored in the SQL. If you really want to store in the file format indeed can but security and weight of the node is matters. |
Hi @ravikoppula thanks for your answer. I was hoping for a quicker solution (like saving the Thanks again for your help! |
@ThomasSquall I believe what @ravikoppula means is to create a MySQL/Postgres column of the JSON data type. This way you can just store the output of |
Hello everyone, I'm implementing flowy in an application with Laravel/MySQL backend.
I'm using the
flowy.output()
function to extract the diagram and send it to the backend through ajax in charge of storing the diagram for future updates.The issue here is that storing it in the DB easily results in "SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'html' at row 1" (roughly with 8/10 nodes).
I was thinking to store the diagram in a file but first I wanted to ask you if you have a better approach.
Thanks all!
The text was updated successfully, but these errors were encountered: