Ann W. Harrison wrote:

>At 12:26 PM 10/29/2001 -0200, C R Zamana wrote:
>
>> Please, is there any problem in "nested transactions"? I'm asking
>>because
>>the routine where the problem arises use this feature: there is one
>>transaction ( the child )
>>to get the number of columns and the parent trasaction, the get the
>>"structure" of a
>>table.
>>
>
>InterBase/Firebird don't support nested transactions - a single connection
>can have several transactions active, but they are independent of each
>other and can, in fact, deadlock against each other - think of them as
>siblings rather than parent & child.
>

Thanks Ann and Paul Reeves: this was the problem.

Best regards.