It would not be wrong to backport this fix to 10.0, I didn't have a 10.
0 client so didn't do it. At this point I hope most people would be
running 10.1.
Andrew McIntyre (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1854?page=comments#action_12438278 ]
Andrew McIntyre commented on DERBY-1854:
----------------------------------------
Should this also be ported to 10.0, since the fix for DERBY-655 which caused
this regression was also ported there?
SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a
primary key and a foreign key
------------------------------------------------------------------------------------------------------
Key: DERBY-1854
URL: http://issues.apache.org/jira/browse/DERBY-1854
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.1.3.1, 10.1.3.0
Environment: Reproduced on Linux, Win2k, and WinXP running JDK 1.4.2.x
Reporter: Chad Loder
Assigned To: Suresh Thalamati
Priority: Critical
Fix For: 10.2.1.5, 10.3.0.0, 10.1.4.0
Attachments: derby-1854-andrew-10.1.diff, derby-1854.diff,
derby-1854_v1.diff
Running the following short SQL script from ij will cause an error "ERROR XSAI2: The
conglomerate (817) requested does not exist.". It appears that the
SYSCS_COMPRESS_TABLE function corrupts tables that have a single column which is both a
primary key and a foreign key.
connect 'jdbc:derby:/testdb;create=true';
CREATE TABLE users (
user_id INT NOT NULL GENERATED BY DEFAULT AS IDENTITY,
user_login VARCHAR(255) NOT NULL,
PRIMARY KEY (user_id));
CREATE TABLE admins (
user_id INT NOT NULL,
PRIMARY KEY (user_id),
CONSTRAINT admin_uid_fk FOREIGN KEY (user_id) REFERENCES users (user_id));
INSERT INTO users (user_login) VALUES('TEST1');
INSERT INTO admins VALUES (VALUES IDENTITY_VAL_LOCAL());
CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP', 'ADMINS', 0);
SELECT * from admins;
