Re: WARNING 02000 (was "Error 00200")

2008-01-31 Thread Daniel John Debrunner
Stanley Bradbury wrote: Hi Nick - This seems to be an IJ issue with updates and deletes (maybe others but not a SELECT statement). I only see this message using IJ - it does not happen when executing the same SQL in a JDBC program and I never get the message in the derby.log file. Have you s

Re: WARNING 02000 (was "Error 00200")

2008-01-31 Thread Stanley Bradbury
Williamson, Nick wrote: -Original Message- From: Stanley Bradbury [mailto:[EMAIL PROTECTED] Sent: 31 January 2008 16:04 To: Derby Discussion Subject: Re: WARNING 02000 (was "Error 00200") Hi Nick - Warnings messages should only be displayed when the derby.stream.error.logSev

RE: WARNING 02000 (was "Error 00200")

2008-01-31 Thread Williamson, Nick
-Original Message- From: Stanley Bradbury [mailto:[EMAIL PROTECTED] Sent: 31 January 2008 16:04 To: Derby Discussion Subject: Re: WARNING 02000 (was "Error 00200") Hi Nick - Warnings messages should only be displayed when the derby.stream.error.logSeverityLevel property is s

Re: WARNING 02000 (was "Error 00200")

2008-01-31 Thread Stanley Bradbury
Williamson, Nick wrote: Sorry - typo in the thread title. Should have been "WARNING 02000". -Original Message- From: Williamson, Nick Sent: 31 January 2008 11:50 To: 'Derby Discussion' Subject: Error 00200 Hi all, I'm running 10.3 and I get this message several times in the Derby