Re: Please try your applications with 10.2 optimizer changes
Army wrote: Kathey Marsden wrote: The DERBY-781 fix is not included with the latest snapshot, but you can get it with the latest unofficial builds that Ole posts at:: http://www.multinet.no/~solberg/public/Apache/Derby/builds/ Actually, I don't think the DERBY-781 changes haven't been committed yet. They were reviewed and received a +1 to commit, but they haven't gone in yet. Similar situation for DERBY-1357... Changes for DERBY-781 and DERBY-1357 have been in since build 423989. Latest build, 425134, is available here: http://www.multinet.no/~solberg/public/Apache/Derby/builds/ Army
Re: Please try your applications with 10.2 optimizer changes
Kathey Marsden wrote: The DERBY-781 fix is not included with the latest snapshot, but you can get it with the latest unofficial builds that Ole posts at:: http://www.multinet.no/~solberg/public/Apache/Derby/builds/ Actually, I don't think the DERBY-781 changes haven't been committed yet. They were reviewed and received a +1 to commit, but they haven't gone in yet. Similar situation for DERBY-1357... Users who are looking to try applications with the 10.2 changes might want to wait until *both* of those changes are checked in before running their tests... Army
Re: Please try your applications with 10.2 optimizer changes
Army wrote: Users who are looking to try applications with the 10.2 changes might want to wait until *both* of those changes are checked in before running their tests... Or try now and when the DERBY-781 changes are committed. The earlier the feedback the better chance of it being addressed in 10.2 release. Dan.
Re: Please try your applications with 10.2 optimizer changes
Daniel John Debrunner wrote: Or try now and when the DERBY-781 changes are committed. The earlier the feedback the better chance of it being addressed in 10.2 release. Yes, definitely worth testing now. There has been a great deal of code change in the past year that might affect users. The optimizer changes are one area but there are lots of others too. Exceptions have changed significantly in the client. With the introduction of JDBC 4.0, I am guessing DatabaseMetaData and ResultSetMetaData are high risk areas for any application that depends on them. Also I think that LOBS are another area were folks should definitely test after significant changes like DERBY-326/DERBY-721. Our known list of changes that may affect existing applications is at: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=10594customfield_12310090=Existing+Application+Impactsorter/field=issuekeysorter/order=ASCsorter/field=updatedsorter/order=DESCsorter/field=prioritysorter/order=DESCrg/jira/secure/ConfigureReport.jspa?filterid=12310892 I have not done a complete pass of the changes and think there are probably more. One interesting thing to look at to identify other risk areas is the results of running the 10.1 tests against 10.2. Just by scanning the new output you might spot something that will affect your app. You can see these test results at: http://people.apache.org/~kmarsden/10_1_tests_10_2_derby/ For example in connectionJdbc20 you can see the new exception for DERBY-721. *** Start: connectionJdbc20 jdk1.4.2_07 DerbyNetClient derbynetmats:jdbc20 2006-06-27 00:44:04 *** 2a3,5 java.sql.SQLException: Stream of column value in result cannot be retrieved twice Kathey
