[
https://issues.apache.org/jira/browse/DERBY-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756089#action_12756089
]
Bryan Pendleton commented on DERBY-4376:
----------------------------------------
Ha! I misread your comment at first and it made me do a double-take.
Then I re-read it, and realized that you meant "missing tests of duplicate
values" :)
To keep this comment from being entirely light-hearted, I think your overall
approach
(refactoring the logic so that MPTSRS can override it more cleanly) sounds
excellent.
> Simple select runs forever
> --------------------------
>
> Key: DERBY-4376
> URL: https://issues.apache.org/jira/browse/DERBY-4376
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4, 10.5.3.0, 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: derby-4376-1a.diff, derby-4376-1a.stat
>
>
> On Derby 10.3.1.4 and later, I see that evaluating the statements below in ij
> apparently makes Derby go into an infinite loop. The select statement ran for
> two hours until I aborted it. I do not see this problem on Derby 10.2.2.0 or
> earlier.
> ij> create table t(x int primary key);
> 0 rows inserted/updated/deleted
> ij> prepare ps as 'select * from t where x=? or x=?';
> ij> execute ps using 'values (cast(null as int), 0)';
> IJ WARNING: Autocommit may close using result set
> X
> -----------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
