"Connection Closed before request completed" error when update with long string on SQL Server
See original GitHub issueI have a table in SQL Server with a column of type varbinary. I use STRING.BINARY to model the column in Sequelize.
signature: {
type: DataTypes.STRING.BINARY,
allowNull: true,
field: 'Signature',
get() {
let s = this.getDataValue('signature');
if (s) {
let buf = Buffer.from(s);
return buf.toString('base64');
} else {
return null;
}
},
set(val) { /* not working. Sequelize stop generating create/update statement. */
let buf = Buffer.from(val, 'base64');
this.setDataValue('signature', buf);
},
},
I use GraphQL to create service. So the signature column uses base64 string type in the API. In the get() method, I convert the binary data to base64 string and it is working fine. But how do I set the base64 string to binary type in the set() method?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
node.js - Connection closed before request completed
I am trying to connect to Azure SQL DB ...
Read more >An existing connection was forcibly closed (OS error 10054)
Describes scenarios in which an existing connection was forcibly closed by the remote host and provides resolutions for these scenarios.
Read more >Common Reasons Why Connections Stay Open for a Long ...
Some of the most common issues that can lead to connections staying open for longer than intended are the following: Applications Not Properly...
Read more >2 Server Error Message Reference - MySQL :: Developer Zone
Each server error message includes an error code, SQLSTATE value, ... Message: The data source connection string '%s' is not in the correct...
Read more >SQL Connection Strings tips
How to connect SQL Server using a connection string. We can use the following connection string for the SQL Server authentication. In this...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It looks like a problem with tedious. I file a new issue there. tedious issue 923.
Looks like increase the tedious packet size could solve the problem.
But I don’t know how it will affect the perfornance. Also whether I can set it just on a query by query basis.