You are right and you are wrong at the same time, and I think that I
just missed something that Jiri announced somewhere :-)
You are right, because using the FBConnectionStringBuilder solves the
problem. You are wrong because it has nothing to do with setting an
explicitly empty role (onl
Why not use the FBConnectionStringBuilder?
That is what I always do and indeed, I don't set the role explicitly to empty.
So this might indeed be your problem.
-Oorspronkelijk bericht-
Van: André Knappstein [mailto:knappst...@beta-eigenheim.de]
Verzonden: maandag 5 november 2012 14:48
Hello Alexander,
maybe there is some difference between
- not assigning a role at all
- assigning "Role = "+String.Empty
Sounds strange, but I will try this out, just in case.
> Hi
> I migrated from 2.6 and 2.7 to 3.0 without changing any code.
> I also never fill in the role.
> It must be some
I attach examples inline (is attaching .txt files or even .png to
the list OK, by the way?)
I used debugger to display them after reading from file and
decryption. I see that I should TRIM the username field :-)
#1 and #3 are examples for connection strings that are working, #2 i
Hi
I migrated from 2.6 and 2.7 to 3.0 without changing any code.
I also never fill in the role.
It must be something else.
-Oorspronkelijk bericht-
Van: Jiri Cincura [mailto:disk...@cincura.net]
Verzonden: maandag 5 november 2012 12:32
Aan: For users and developers of the Firebird .NET
How the complete connection string looks like?
On Mon, Nov 5, 2012 at 12:14 PM, André Knappstein
wrote:
> I noticed a change which I did not read about before.
> Maybe I missed it, maybe it was not announced.
> My last installed version was 2.6. on most seats, 2.75 on some.
>
> If "Role = " (empt
I noticed a change which I did not read about before.
Maybe I missed it, maybe it was not announced.
My last installed version was 2.6. on most seats, 2.75 on some.
If "Role = " (empty string), the connection string now is invalid.
I will have to roll back to 2.6 for now, because I will first ha
