I'm not even sure if there is a way to "code around" the bug. The only solution I know of that doesn't require modifying torque is to implement your own retrieve method in the Peer. In which case modifying the retrieveByPK method would not have any effect.
It seems that it's too late now, with people voting for the 3.0 release. I'm disapointed that I will not be able to use the 3.0 release without a number of patches in my system. -james On Wed, 2002-11-27 at 14:31, Quinton McCombs wrote: > > Issue TRQS9 has just been modified by user quintonm > > You can view the issue detail at the following URL: > <http://scarab.werken.com/scarab/issues/id/TRQS9> > > The following modifications were made to this issue: > > It may be broken but people have coded around the bug. Changing the way results of >this method will break existing code. According to the jakarta rule for modifing a >public interface, a new method should be created. The old one should be deprecated. > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- James A. Hillyerd <[EMAIL PROTECTED]> Java Software Engineer - http://www.whynotown.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
