Re: [jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-08-03 Thread Kathey Marsden
Dag H. Wanvik wrote: I think iregression is good to keep for history. A fixed regresssion is a fixed regression and that makes sense. Existing application impact is a tool for users so should reflect the current state. Does anyone know if is it explained elsewhere? If not, I think it would

Re: [jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-08-03 Thread Dag H. Wanvik
"Kathey Marsden (JIRA)" writes: > [ > http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12425609 > ] > > Kathey Marsden commented on DERBY-1252: > --- > > now that this is fixed , is there still existing application impact

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-08-03 Thread Kathey Marsden (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12425609 ] Kathey Marsden commented on DERBY-1252: --- now that this is fixed , is there still existing application impact? If not then we should uncheck the box. "Existi

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-08-03 Thread Rick Hillegas (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12425602 ] Rick Hillegas commented on DERBY-1252: -- Thanks, Dag. The fix looks solid. Derbyall had two diffs for me: 1) the wisconsin noise, 2) XATest under DerbyNetClien

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-08-01 Thread Dag H. Wanvik (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12425042 ] Dag H. Wanvik commented on DERBY-1252: -- Two patches are uploaded to solve this issue. derby1252-10.1.{diff,stat} derby1252.{diff,stat} The first pa

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-07-27 Thread Dag H. Wanvik (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423879 ] Dag H. Wanvik commented on DERBY-1252: -- Yes, that's what I had in mind for my "alternative two" above. If people are OK with that approach I can make a patch f

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-07-27 Thread Rick Hillegas (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423873 ] Rick Hillegas commented on DERBY-1252: -- It seems to me that SYSIBM.METADATA exists to support the JCC driver. Maybe we could let this procedure continue to re

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-07-25 Thread Dag H. Wanvik (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423343 ] Dag H. Wanvik commented on DERBY-1252: -- Impact: This regression affects client which do not support updatable, scrollable, insensitive result sets; i.e. JCC a

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-07-24 Thread Daniel John Debrunner (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423191 ] Daniel John Debrunner commented on DERBY-1252: -- How would this regression manifest itself in a working application? > Old clients with new server retu

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

2006-07-24 Thread Kathey Marsden (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423188 ] Kathey Marsden commented on DERBY-1252: --- This issue is a regression. It would be ideal to release Derby 10.2 without any known regressions so we don't have