Subject | Re: [Firebird-Architect] DDL, Scripts, DFW, and Commit |
---|---|
Author | Jim Starkey |
Post date | 2004-04-29T11:27Z |
David Jencks wrote:
operations, whether DYN (for backwards compatibility) or SQL DDL should
create an ad hoc transaction, perform the necessary system table
transformations, and commit the transaction. There is no reason to
support pending DDL changes.
>Although it looks most like an airport name, it means deferred workIt's not only possible, it's the desirable way to do it. Any DDL
>
>I'm reluctant to see ddl become autocommit only. Is there any way to
>require it to be in a tx with no dml or no update dml?
>
>
operations, whether DYN (for backwards compatibility) or SQL DDL should
create an ad hoc transaction, perform the necessary system table
transformations, and commit the transaction. There is no reason to
support pending DDL changes.
>
>
>