>
> Subject: Re: [Firebird-net-provider] Connection to Firebird 3 With
> Legacy Authentication Fails
> To: "For users and developers of the Firebird .NET providers"
> <firebird-net-provider@lists.sourceforge.net>
> Message-ID: <5725d541.8090...@lawinegevaar.nl>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 29-4-2016 08:26, LtColRDSChauhan wrote:
> > Mark,
> > Could trace your:
> > https://github.com/FirebirdSQL/jaybird/wiki/Jaybird-and-Firebird-3
> > It covers everything except for SEC$USER_NAME, SEC$NAME_PART.
>
> As far as I know doing things for SEC$USER_NAME, SEC$NAME_PART should
> not be necessary for 'normal' Firebird 2.5 database upgraded to Firebird
> 3. It seems very specific for your database or maybe if you downgraded a
> Firebird 3 database to 2.5 and then back to 3 (?).
>
> Mark
>
You are correct, Mark.
Thanks a lot.
Rajiv
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider