configuration parameters gets ignored if connecting with websockets

[Gioee]

Current Behavior

configuration parameters gets ignored if connecting with websockets

Expected Behavior

configuration parameters like maxdata, maxrows, maxrowset, etc. should work

Steps to Reproduce the Problem

1. Initialize a connection with websockets with optional parameters

Environment

• Version: 1.308
• Platform: Mac
• Node.js Version: v20.12.2

[Gioee]

This is the method that gets used with tls in the driver getInitializationCommands we should update the driver and the gateway

[jacobprall]

What's the status on this?

[danielebriggi]

they have the workaround, this bug solves the incoherent behavior of the way to customize the connection parameters

[jacobprall]

“Incoherent” is there a fix needed on our side?

[danielebriggi]

yes, connection should be configurable even when is established via websocket

[Gioee]

@jacobprall I haven't prioritised it as high because it's not a breaking bug. The user can still set these parameters from the connection string or directly in a query. It's certainly something we have to work on because right now it's not that intuitive.