sasha wrote:
> Hi! I've tried to use provider with FB 2.1 and there were a broblems
> with new FB protocol:
>
> http://tracker.firebirdsql.org/browse/CORE-1218
>
> But vlad said that provider should not only check isc_info_end, but
> array length too. So i propose to make some changes in Statem
Jiri Cincura wrote:
> Carlos Guzmán Álvarez wrote:
>> That is why we need to check the changes in firebird 2.1, check how they
>> affect the provider, create a new GDS implementation and add a new
>> Server Type.
>
> I agree.
>
Carlos, Jiri, it looks like it was bad idea to use Jaybird as a
r
Carlos Guzmán Álvarez wrote:
> That is why we need to check the changes in firebird 2.1, check how they
> affect the provider, create a new GDS implementation and add a new
> Server Type.
I agree.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
--
Hello:
> AFAIK no. The compatibility is only old clients =3D> new server. The new =
> client must use some "old" stuff to be able to work with old server.
>
That is why we need to check the changes in firebird 2.1, check how they
affect the provider, create a new GDS implementation and add a ne
Madhu Sasidhar, MD wrote:
> Can we not preserve old protocol in Provider and use a property to use
> new protocol/old protocol?
If you will not preserve code for protocol, what will be the purpose of
the property?
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
Can we not preserve old protocol in Provider and use a property to use new
protocol/old protocol?
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of you
Carlos Guzmán Álvarez wrote:
> That is fine, but the question is whether a 2.1 client will connect
> against a 2.0/1.5/1.0 server ??
AFAIK no. The compatibility is only old clients => new server. The new
client must use some "old" stuff to be able to work with old server.
--
Jiri {x2} Cincura
Hello:
> New GDS implementation is other question.
>
> Vlad told me that new protocol should be 100% compartiable with old
> protocol, i.e. all old clients should work with 2.1 but without new
> optimization.
>
> Ant it's really so. I've downloaded lastest 2.1 snapshot build and tried
> it
sasha wrote:
>> For 2.1 more than probably we will need a new GDS implementation, that
>> will depend on the changes on the remote protocol, i need to check what
>> are have been done in the server.
>
> New GDS implementation is other question.
>
> Vlad told me that new protocol should be 100% co
> For 2.1 more than probably we will need a new GDS implementation, that
> will depend on the changes on the remote protocol, i need to check what
> are have been done in the server.
New GDS implementation is other question.
Vlad told me that new protocol should be 100% compartiable with old
pro
Hello:
But shouldn't be the ProcessRecordsAffectedBuffer method be improved too
(and some others on other place (i.e. ParseQueryInfo from FbService, etc.),
that are checking IscCodes.isc_info_end)?
For 2.1 more than probably we will need a new GDS implementation, that
will depend on the changes
Hi, nice job.
But shouldn't be the ProcessRecordsAffectedBuffer method be improved too
(and some others on other place (i.e. ParseQueryInfo from FbService,
etc.), that are checking IscCodes.isc_info_end)?
So I suppose to check (and improve) these methods and then test the
changes. If Carlos ha
Hi! I've tried to use provider with FB 2.1 and there were a broblems
with new FB protocol:
http://tracker.firebirdsql.org/browse/CORE-1218
But vlad said that provider should not only check isc_info_end, but
array length too. So i propose to make some changes in StatementBase.cs
in method Par
13 matches
Mail list logo
