db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik" <dag.wan...@oracle.com>
Subject Implicit commit and end of SYSCS_UTIL.SYSCS_IMPORT_TABLE?
Date Mon, 04 Nov 2013 16:37:48 GMT
Hi,

I read our reference manual for import table, but it doesn't mention 
this. Can anyone explain why we
do an implicit commit? I thought the import statement was transactional; 
I can imagine
it's because with replace option we truncate the old table would roll 
back not via the log but by undoing the creation of a replacement 
conglomerate.

In any case, the reference manual should mention this prominently, I think.

Code reference: line 1580
http://svn.apache.org/viewvc/db/derby/code/branches/10.10/java/engine/org/apache/derby/catalog/SystemProcedures.java?view=markup

I'll file a doc issue if this is as it should be.

Thanks,
Dag

Mime
View raw message