> -Original Message-
> From: Alex Peshkoff [mailto:peshk...@mail.ru]
> Sent: Lunes, 03 de Marzo de 2014 5:28
>
> On 03/02/14 11:32, Claudio Valderrama C. wrote:
> > Hello, I have two doubts concerning gbak in v3:
> >
> > 1.- Should rdb$linger be stored in the backup?
>
> I think yes
Don
03.03.2014 13:39, Dimitry Sibiryakov wrote:
>> If it's really not used anywhere else (i.e. comment is correct) - not.
>
> It may be informative field to get field limit in characters instead of
> bytes. The fact
> that it is not used in the engine doesn't mean that it cannot be used by
> applica
03.03.2014 10:27, Alex Peshkoff wrote:
>> 3.- We have this in restore for rdb$relation_fields:
>> >case att_field_character_length:
>> >field->fld_character_length = (USHORT) get_numeric(tdgbl);
>> >break;
>> >
>> >However, as the old comment indicates
>> >SSHORT fld_character_length; // on
On 03/02/14 11:32, Claudio Valderrama C. wrote:
> Hello, I have two doubts concerning gbak in v3:
>
> 1.- Should rdb$linger be stored in the backup?
I think yes
> 2.- Is this a small bug?
> // TYPE relation attributes
> att_type_name = SERIES,
> att_type_type,
> att_type_f
Hello, I have two doubts concerning gbak in v3:
1.- Should rdb$linger be stored in the backup?
2.- Is this a small bug?
// TYPE relation attributes
att_type_name = SERIES,
att_type_type,
att_type_field_name,
att_type_description,
att_type_system_fla
