Helen Borrie wrote:

>SQL language is split into two kinds of statements: those that define your
>schema (data definition language, or DDL) and those that manipulate data
>(data manipulation language, or DML).
>
>
>

Ah! I knew that. I just never used the terms. Thanks for the reminder.

>When you are performing DDL - yes, if you don't really understand what you
>are doing then it won't hurt to commit after every DDL statement until you
>get your head around which sorts of DDL can be committed in batches. When
>performing DML (SELECT, INSERT, UPDATE, DELETE) you often don't want to
>commit after every statement.
>
>Just be safe and keep DDL and DML separate.
>
>
>

That's what I have, DML and DDL in two dfferent files.

>Ask in the Jaybird list. From observation, I think Jaybird makes a lot of
>use of autocommit transactions.
>
>
>

Possible, I'll see. It's possible that the problem stems from incorrect
autocommit or something.

Thanks,

L