> Binary data should be able to be represented with hexadecimal. And,
Good point.
> We are looking at implementing our own encryption plugin, but still
> undecided how the key will be passed, since our application uses a mix
> of Delphi(IBDAC) and C#(EF6). Our initial thought is that it will
Hi,
At July 12, 2017, 5:44 AM, Jiří Činčura wrote:
>> I think it makes more sense on the connection string. It already contains
>> sensitive info (username,password) and needing to provide connection
>> related info by another method would be counter intuitive.
> Good point.
> In my thinking I
> Which would not be true anymore, except if you add EncryptionKey to
> connection string parsing anyway.
Of course I would. The builder and connection string options are in
sync.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
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,
> 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
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.
I think it makes more sense on the connection string. It already contains
sensitive info (username,password) and needing to provide connection
related info by another method would be counter intuitive.
On 12 July 2017 at 08:55, Jiří Činčura wrote:
> Hi *,
>
> thanks to