db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Possible SYSCS_COMPRESS_TABLE bug
Date Mon, 24 May 2010 13:14:07 GMT
On 05/24/10 07:44 AM, Brett Mason wrote:
> Hi there,
>
> I think I have encountered a bug in Derby and I just wanted to check if this
> was already a known issue.
>
> It appears that running SYSCS_UTIL.SYSCS_COMPRESS_TABLE on a table with a
> null-able unique constraint will disable the unique constraint. The script
> below should reproduce the problem. The expected behaviour is for the second
> insert to fail due to the unique constraint but instead it is allowed. The
> second insert will fail as expected either if the call to
> SYSCS_COMPRESS_TABLE is skipped or if the column is declared NOT NULL.
>
> I have reproduced the problem using embedded Derby 10.5.1.1, 10.5.3.0 and
> 10.6.1.0 using ij.
>
> If this turns out to be a new bug I am happy to enter it in JIRA.
>   

Hi Brett,

This does indeed look like a bug. Please go ahead and file it in JIRA.

Thanks,

-- 
Knut Anders


Mime
View raw message