18.06.2016 16:03, Mark Rotteveel wrote:
> What about op_reconnect? Can I always send an 8 byte VAX 'integer', even
> on older Firebird versions? Or should I only try to send 8 bytes on FB 3?
The latter. Older FB versions are unlikely to crash but won't execute
the request either (VAX integers
On 18-6-2016 15:03, Mark Rotteveel wrote:
> Yet another question:
>
> What about op_reconnect? Can I always send an 8 byte VAX 'integer', even
> on older Firebird versions? Or should I only try to send 8 bytes on FB 3?
The same question also applies to isc_reconnect_transaction in fbclient.
Mark
On 17-6-2016 20:23, Mark Rotteveel wrote:
> On 2-5-2016 08:40, Dmitry Yemanov wrote:
>> 01.05.2016 13:01, Mark Rotteveel wrote:
>>>
But it seems that these inputs tags were forgotten re. their longer
counterparts: isc_spb_rpr_commit_trans, isc_spb_rpr_rollback_trans,
On 06/17/2016 09:23 PM, Mark Rotteveel wrote:
> On 2-5-2016 08:40, Dmitry Yemanov wrote:
>> 01.05.2016 13:01, Mark Rotteveel wrote:
But it seems that these inputs tags were forgotten re. their longer
counterparts: isc_spb_rpr_commit_trans, isc_spb_rpr_rollback_trans,
17.06.2016 21:23, Mark Rotteveel wrote:
>
> Does this BigIntSpb also work with a v2 SPB, or do I need to change it
> to a v3 SPB (code suggests v2 will work, but confirmation would be nice)?
It works.
> Is there an easy trick to get Firebird to produce a 33 bit or longer
> transaction id without
> Is there an easy trick to get Firebird to produce a 33 bit or longer
> transaction
> id without having to commit 32^2 + 1 transactions so I can check if my
> implementation will work with FB 3.0.1?
Hack the header of an existing database file with a Hex editor?
Sean
On 2-5-2016 08:40, Dmitry Yemanov wrote:
> 01.05.2016 13:01, Mark Rotteveel wrote:
>>
>>> But it seems that these inputs tags were forgotten re. their longer
>>> counterparts: isc_spb_rpr_commit_trans, isc_spb_rpr_rollback_trans,
>>> isc_spb_rpr_recover_two_phase. Please file a ticket.
>>
>> Done:
01.05.2016 13:01, Mark Rotteveel wrote:
>
>> But it seems that these inputs tags were forgotten re. their longer
>> counterparts: isc_spb_rpr_commit_trans, isc_spb_rpr_rollback_trans,
>> isc_spb_rpr_recover_two_phase. Please file a ticket.
>
> Done: http://tracker.firebirdsql.org/browse/CORE-5224
On 30-4-2016 18:21, Dmitry Yemanov wrote:
> 30.04.2016 18:47, Mark Rotteveel wrote:
>
>> Is the limit now 2^32 or 2^48?
>
> 2^48 internally, represented as 2^64 for the external world.
>
>> Also what is the effect of this change (and the change "Limits Raised
>> for Attachment and Statement IDs"
30.04.2016 18:47, Mark Rotteveel wrote:
> Is the limit now 2^32 or 2^48?
2^48 internally, represented as 2^64 for the external world.
> Also what is the effect of this change (and the change "Limits Raised
> for Attachment and Statement IDs" below that) for the wire protocol?
> Does this affect
I find the text in the release notes of Firebird 3 for "Extension of
Transaction ID Space Limit"
(http://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-apiods.html#rnfb30-apiods-transaclimit
) a bit low on information and a bit confusing.
Especially this is confusing:
11 matches
Mail list logo
