Skip to content

configuration parameters gets ignored if connecting with websockets #119

Open

Description

@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

Activity

  1. added
    bugSomething isn't working
    on Nov 5, 2024
  2. Gioee commented on Nov 5, 2024

    @Gioee
    MemberAuthor

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

  3. jacobprall commented on Nov 12, 2024

    @jacobprall

    What's the status on this?

  4. danielebriggi commented on Nov 12, 2024

    @danielebriggi
    Member

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

  5. jacobprall commented on Nov 13, 2024

    @jacobprall

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

  6. danielebriggi commented on Nov 13, 2024

    @danielebriggi
    Member

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

  7. Gioee commented on Nov 13, 2024

    @Gioee
    MemberAuthor

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions