Re: [Firebird-net-provider] Bug with multiple commands in same transaction

[Pierre A. <pie...@op...>]

Carlos Guzm=E1n =C1lvarez wrote:
>> Certainly not, transactions are conceptualy for making a serie of SQL
>> command, and then commit (or rollback) all of them if ok (or not)
>>
>> (1) START TRANSACTION
>> (2) CREATE TABLE X(A INTEGER NOT NULL, B INTEGER);
>> (3)  INSERT INTO X(A, B) VALUES (1,1);
>> (4) COMMIT / END TRANSACTION
>
> I think it's working ok.
>
> The CREATE TABLE is a DDL command and i think that will be not possible
> to make anything with the table until the transaction is commited.

I just ran the following script in IBExpert's "Script Executive",
and it works just fine :

CREATE TABLE X(A INTEGER NOT NULL, B INTEGER);
INSERT INTO X(A, B) VALUES (1,1);
COMMIT WORK;

I don't see why the table creation should not be visible from within
the transaction. This would be really silly !?

> I have make the same test using IBExpert and raises the same error.

See my example; does it raise an error in your IBExpert ?

> If i'm wrong, please correct me :)

I am no SQL guru, but the fact that a table is not visible unless
the full transaction is commited does not make sense to me.

    Pierre