> I agree with you, but in software everythink has a solution.
> Solution for this could be like firebird versions.
>
> For FB Version 2.X we could have FB .Net provider 2.X.Y where Y is udate
> version for X release of FB 2 server.
In my opinion a solution would be an installation package Fireb
> Oleg Deribas wrote:
> > Hello,
>
> So, _unless_ there is coordinated release plan for the whole Firebird
> Project _and_ the release dates will be met by all subproject under any
> condition, tieing the driver release numbers to the Firebird RDBMS
> release numbers is not reallistic.
>
> Roma
Oleg Deribas wrote:
> Hello,
>
> Mercea Paul said the following on 02.07.2007 21:08:
>
>> Could Fb.Net Provider have release number specific to Firebird server?
>> If Current provider support all facilities for FB 2.1 Beta 1, could have
>> same release number as fb server (2.1)? It's more easy to
Hello,
Mercea Paul said the following on 02.07.2007 21:08:
> Could Fb.Net Provider have release number specific to Firebird server?
> If Current provider support all facilities for FB 2.1 Beta 1, could have
> same release number as fb server (2.1)? It's more easy to know what provider
> is compat
Hi Carlos, Jiri
Could Fb.Net Provider have release number specific to Firebird server?
If Current provider support all facilities for FB 2.1 Beta 1, could have
same release number as fb server (2.1)? It's more easy to know what provider
is compatible with witch server!
Maybe I'm wrong...
Best re
Hello:
> To FirebirdClient no.
>
> Are you planning to build also WebProviders?
Not for the devel version ( 2.5.0 )
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express a
On 7/2/07, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote:
> Jiri do you have some pending commits ??
To FirebirdClient no.
Are you planning to build also WebProviders?
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
