[ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12421965 ] Deepa Remesh commented on DERBY-1029: -------------------------------------
I have not looked at the whole patch but I just noticed this patch updates a master file 'procedureInTrigger.out'. I had used "true" in the sql for this test without remembering boolean work will be backed out. ij> --- check index is not created select count(*) from SYS.SYSCONGLOMERATES where CONGLOMERATENAME='IX' and ISINDEX=true; -1 ------------ -0 +ERROR 42X01: Syntax error: true. Once boolean is backed out, this will not cover the intended test. I think the above sql can be changed to use "1" instead of "true" to cover the intended test. I would appreciate if you can handle this change in this patch. > Backout boolean work from the 10.2 branch immediately after the branch is > created > --------------------------------------------------------------------------------- > > Key: DERBY-1029 > URL: http://issues.apache.org/jira/browse/DERBY-1029 > Project: Derby > Issue Type: Sub-task > Components: SQL > Affects Versions: 10.2.0.0 > Reporter: Kathey Marsden > Assigned To: Rick Hillegas > Priority: Blocker > Fix For: 10.2.0.0 > > Attachments: derby-1029_v03.diff > > > There was discussion on the list regarding how to handle this issue but keep > the BOOLEAN work for inclusion in future releases. The approach discussed > was to back the DERBY-499 work out of the 10.2 branch as soon as it is > created, but leave it in the trunk > I think this an acceptable solution but only if we can get someone assigned > to this issue that is willing to commit now to doing that work as soon as we > branch. The reverse merge may be messy at that point do to other changes > that have gone in. > > Is there someone who will volunteer to do this work and assign themselves to > this issue? -- 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
