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

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

Carlos Guzm=E1n =C1lvarez wrote:
>> CREATE TABLE X(A INTEGER NOT NULL, B INTEGER);
>> INSERT INTO X(A, B) VALUES (1,1);
>> COMMIT WORK;
>
> I have tested it from the sql editor of ib expert, but just test this i=
n
> the script executive:
>
> CREATE TABLE X(A INTEGER NOT NULL, B INTEGER);
>
> You are not going to get a message telling that there are uncommited
> statements ( this message appears if you exec only the insert for
> example ), i think that they are making an autocommit for DDL
> statements, as ISQL makes by default.

You mean that after every DDL statement, I have to do a commit also
on my own. This seems pretty weird.

But I have to agree with you: IBExpert seems to be committing its
work automagically.

> Has you tested the sample i have sent for ISQL ??

I don't have ISQL, but I believe what you tell me. It just seems
really strange. Adding the "SET AUTODLL OFF;" line in IBExpert
causes also IBExpert to generate an error on the INSERT statement.


So how can I do what I want, namely create a table and fill it
in, then rollback the table creation ?

Thanks a lot.

    Pierre