-Original Message-
From: Alex Peshkoff [mailto:peshk...@mail.ru]
Sent: Lunes, 16 de Abril de 2012 7:22
'Hard' limit can be reached only by gbak's attachment. I.e.
with transaction ID
use of ~0 as special condition should be OK. Certainly, check
for 'hard' limit should be
17.04.2012 12:53, Claudio Valderrama C. wrote:
Ok, I would like to create a type. If
typedef ULONG TxnType;
is too awkward, suggest something better.
Because it is not a transaction itself, but only it's id, I would suggest
tid_t...
--
SY, SD.
Ok, I would like to create a type. If
typedef ULONG TxnType;
is too awkward, suggest something better.
Don't name it TxnType, please. It is transaction *number* and not
an isolation level, for example. We already have RecordNumber and
PageNumber, let be consistent.
Regards,
Vlad
17.04.2012 14:53, Claudio Valderrama C. wrote:
Ok, I would like to create a type. If
typedef ULONG TxnType;
is too awkward, suggest something better.
TxnId or txn_id_t or something like that.
Dmitry
--
Better than
On 04/17/12 14:53, Claudio Valderrama C. wrote:
Second, is the transaction type something exclusive to JRD? If yes, it can
be defined in Jrd; if not, it will have to be defined in fb_types.h because
I don't want to deal with circular dependencies.
It can get out from jrd in at least 2 cases
17.04.2012 12:12, Alex Peshkoff wrote:
It can get out from jrd in at least 2 cases - in system context variable
and in monitoring tables.
Also in the results of isc_transaction_info and isc_database_info.
--
SY, SD.
17.04.2012 14:53, Claudio Valderrama C. wrote:
Ok, I would like to create a type. If
typedef ULONG TxnType;
is too awkward, suggest something better.
TxnId or txn_id_t or something like that.
Look, currently we have
SLONG tra_number; // transaction number
compare it with
TxnType
17.04.2012 14:20, Vlad Khorsun wrote:
TraNumber tra_number;
From another side, it's isc_info_tra_id in API, TRANSACTION_ID in
context variables and MON$TRANSACTION_ID in the monitoring tables :-)
As for me, both Id and Number are acceptable as suffixes. Just please
don't make it
17.04.2012 14:20, Vlad Khorsun wrote:
TraNumber tra_number;
From another side, it's isc_info_tra_id in API, TRANSACTION_ID in
context variables and MON$TRANSACTION_ID in the monitoring tables :-)
This is another important point. There is user POV and user (public) data
types,
such
-Original Message-
From: Vlad Khorsun [mailto:hv...@users.sourceforge.net]
Sent: Martes, 17 de Abril de 2012 7:05
I'm not insist in Number over ID but Number looks more
consistent for me...
What a sensitive matter! :-)
Ok, let's use TxnNumber or TraNumber; should I define it
17.04.2012 16:34, Claudio Valderrama C. wrote:
Ok, let's use TxnNumber or TraNumber; should I define it in JRD? As I see,
this definition will be only useful for JRD, unless some of you insist that
I put it in fb_types.h.
JRD should be okay.
Second, following the same reasoning, should I
-Original Message-
From: Dmitry Yemanov [mailto:firebi...@yandex.ru]
Sent: Martes, 17 de Abril de 2012 7:44
17.04.2012 16:34, Claudio Valderrama C. wrote:
Ok, let's use TxnNumber or TraNumber; should I define it in
JRD? As I see,
this definition will be only useful for JRD,
RDB$TYPES contain duplicated character sets
---
Key: CORE-3820
URL: http://tracker.firebirdsql.org/browse/CORE-3820
Project: Firebird Core
Issue Type: Bug
Components: Charsets/Collation
13 matches
Mail list logo
