Perhaps you made a change to the code, but forgot to recompile, or forgot to re-update your JAR files, or made some other simple build mistake.
As a technique for understanding the behavior of your program, commenting parts of it in and out and re-running the program is a very good technique, but it is easy to make a simple build mistake and not run the modified version of the program which you think you are running. Another very good technique for understanding the behavior of your program is to run it under a Java debugger, and then you can stop and start it and various points, step through it line by line, look at the values of variables at various points, etc. thanks, bryan On Sat, May 20, 2017 at 11:12 PM, Bob M <rgmatth...@orcon.net.nz> wrote: > The situation has deteriorated.................................. > > I have placed /* */ around all code which adds new trade records and > which > updates trade records > > I was expecting x number of trades to take place and no error messages > > Instead I got the following:- > > Adding a new trade record Number: 4101 > > ----- SQLException ----- > SQL State: 23505 > Error Code: 20000 > Message: The statement was aborted because it would have caused a > duplicate > key value in a unique or primary key constraint or unique index identified > by 'SQL170412104646890' defined on 'TRADES'. > > I checked the whole program for "adding a new trade record" and found only > a > single instance - the code is within the /* */ so how can I continue to > get a reference to these words in an error code? > > Bob M > > > > -- > View this message in context: http://apache-database.10148. > n7.nabble.com/Updating-2-derby-tables-tp147386p147412.html > Sent from the Apache Derby Users mailing list archive at Nabble.com. >
