Not exactly sure what you mean with right away. The reason to not use the
existing ConnectionStringBuilder is that it is implicit that it can be
converted to a string.
Which would not be true anymore, except if you add EncryptionKey to
connection string parsing anyway.

On 12 July 2017 at 13:51, Jiří Činčura <j...@cincura.net> wrote:

> > What about a callback on Connection that returns a Connection Info
> > (ConnectionStringBuilder-like) object.
> > Could also add a connection constructor overload that accepts a
> > Connection
> > Info object.
> > Can then provide all connection data in one place with convenience of not
> > converting from/to a string.
>
> Then the ConnectionStringBuilder can be used right away, no?
>
> --
> Mgr. Jiří Činčura
> https://www.tabsoverspaces.com/
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Firebird-net-provider mailing list
> Firebird-net-provider@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to