Should we take non-connection string options in Client constructor?

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we only accept options to the Client constructor through the connection string. We should decide whether or not to provide the ability to specify options through the constructor outside of the connection string (and if so, whether or not the connection string options should take precedence).

            Assignee:
            David Golden
            Reporter:
            Samuel Rossi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: