DERBY-132 resolved ? Table not automatically compressed --------------------------------------------------------
Key: DERBY-509 URL: http://issues.apache.org/jira/browse/DERBY-509 Project: Derby Type: Bug Versions: 10.1.1.0 Environment: JDK 1.4.2, JDK 1.5.0, Windows XP Reporter: Volker Edelmann I tried a test-program that repeatedly inserts a bunch of data into 1 table and repeatedly deletes a bunch of data. derby.executeSelect("select count(*) c from rclvalues"); TestQueries.executeBulkInsertAnalyst(derby.getConnection(), 2000000); // insert 2.000.000 rows derby.executeDelete("delete from rclvalues where MOD(id, 3) = 0"); TestQueries.executeBulkInsertAnalyst(derby.getConnection(), 1000000); derby.executeDelete("delete from rclvalues where MOD(id, 5) = 0"); derby.executeSelect("select count(*) c from rclvalues"); At the end of the operation, the table contains approximately the same number of rows. But the size of the database has grown from 581 MB to 1.22 GB. From the description of item DERBY-132, I hoped that Derby does the compression now ( version 10.1.X.X.). Did I overlook I still have to use SYSCS_UTIL.SYSCS_COMPRESS_TABLE ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira