Jarek Zgoda wrote:
> Uwe Grauer napisał(a):
>
>> I do not see a commit between the table creation and the generator
>> creation. Maybe this is a problem. In my private tool i do a commit
>> after every object.
>
> Dear sir, DDL statements are processed without commitment control. They
> are committed instantly by db engine one-by-one.
>
No, you are wrong here.
If you don't work with implicit Transactions (no autocommmit) then
the programmer has to decide when to commit or rollback.
Otherwise there wouldn't be a need for Transactions in DDL.
However, in some databases you have no real transaction control
for DDL.
In the old days of Interbase (before this became Firebird) you could
only do 255 DDL-Transactions. Then you had to backup and restore to get
rid of old pending DDL-Transactions.
With this you could even do DDL when other People were using the old
schema. When you started a Transaction you got a snapshot of the schema
of the current DDL-definition.
Firebird has a multigenerational transaction mechanism.
It doesn't do explicit locking like many other engines do.
Regards,
Uwe
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
