private static void compressTable(String tableName,boolean compressInPlace) throws AdeInternalException {
  logger.trace(String.format("compressTable( %s, %b ) -->entry",tableName,compressInPlace));
  logger.warn(String.format("compressTable( %s ) suppressed (currently unsafe!)",tableName));
  logger.trace(String.format("compressTable( %s ) <-- exit",tableName));
}

private static void compressTable ( String tableName , boolean compressInPlace ) throws AdeInternalException { logger . trace ( String . format ( "compressTable( %s, %b ) -->entry" , tableName , compressInPlace ) ) ; logger . warn ( String . format ( "compressTable( %s ) suppressed (currently unsafe!)" , tableName ) ) ; logger . trace ( String . format ( "compressTable( %s ) <-- exit" , tableName ) ) ; }
method for invoking a known database prepared statement to compress a designated table . typically this is done after a nontrivial number of deletions from a table have occurred , and the current database implementation is know to be a lazy space reclaimer ( e . g . , derby ) . notes : at this time , apache derby is the database implementation in use , and derby has a few important " oh by the way ( s ) " : 1 ) either of the prepared statements : syscs_util . syscs_compress_table ( ) syscs_util . syscs_inplace_compress_table ( ) should be called in autocommit mode . this should already be so for a new connection , by default , but as a formality , we ensure it . since we will not reuse the connection object , we will not worry about restoration . 2 ) see the derby documentation for discussion of the < short > parameters to these prepared statements . they have important consequences for the type and duration of processing which occurs . 3 ) in practice , syscs_util . syscs_compress_table ( ) seems to incur deadlock with concurrent anomaly detection engine analyze processing ( and perhaps others , as well ) , whereas syscs_util . syscs_inplace_compress_table ( ) does not seem to . the scoping of this method and the default ( " in place = = true " ) reflects the fact that only the in - place form is trusted by anomaly detection engine at this time ( and so this is currently the only way it is offered publicly ) . note also that both prepared statements acquire an exclusive table lock for their duration . experience shows that explicit acquisition beforehand does not seem to provide any help in avoiding deadlock ( contrary to any internet testimonials one may find ) .
