[ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12421741 ] Rick Hillegas commented on DERBY-1029: --------------------------------------
Contents of this patch are: M java\engine\org\apache\derby\impl\sql\compile\sqlgrammar.jj M java\engine\org\apache\derby\iapi\reference\DRDAConstants.java M java\drda\org\apache\derby\impl\drda\FdocaConstants.java M java\drda\org\apache\derby\impl\drda\SQLTypes.java M java\drda\org\apache\derby\impl\drda\AppRequester.java M java\drda\org\apache\derby\impl\drda\DRDAConnThread.java M java\testing\org\apache\derbyTesting\functionTests\tests\lang\db2Compatibility.sql M java\testing\org\apache\derbyTesting\functionTests\tests\lang\logop.sql M java\testing\org\apache\derbyTesting\functionTests\tests\lang\schemas.sql D java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\lang\BooleanTest.java D java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\lang\default_app.properties D java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\lang\LangSuite.java D java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\lang\build.xml M java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\compatibility\JDBCDriverTest.java M java\testing\org\apache\derbyTesting\functionTests\master\cast.out M java\testing\org\apache\derbyTesting\functionTests\master\db2Compatibility.out M java\testing\org\apache\derbyTesting\functionTests\master\valuesclause.out M java\testing\org\apache\derbyTesting\functionTests\master\procedureInTrigger.out M java\testing\org\apache\derbyTesting\functionTests\master\subquery.out M java\testing\org\apache\derbyTesting\functionTests\master\implicitConversions.out M java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk14\metadata.out M java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk14\syscat.out M java\testing\org\apache\derbyTesting\functionTests\master\logop.out M java\testing\org\apache\derbyTesting\functionTests\master\aggregate.out M java\testing\org\apache\derbyTesting\functionTests\suites\derbylang.runall M java\testing\build.xml M java\client\org\apache\derby\client\net\Typdef.java M java\client\org\apache\derby\client\net\NetStatementRequest.java M java\client\org\apache\derby\client\am\CrossConverters.java M java\client\org\apache\derby\client\am\Cursor.java M java\client\org\apache\derby\client\am\Types.java M java\client\org\apache\derby\client\am\SignedBinary.java M java\client\org\apache\derby\client\am\DatabaseMetaData.java M java\client\org\apache\derby\client\am\ColumnMetaData.java > 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
