db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-159) When Derby runs in Network Server mode, client does not receive warnings generated by Derby
Date Wed, 17 Aug 2005 19:35:28 GMT
I was just doing some jira cleanup to get the issues filed under
some categories, while scanning the unknown issues to see if I
had missed any that applied to the area I was looking at.
I took a guess at the best component.  I left a few which I just
couldn't categorize.

Also I was wondering if the SQL category might be better broken
down into stuff like: parser, compile, execution, and optmizer.

David Van Couvering wrote:
> Thanks, Mike.  I'm working on adding SQLState support for client 
> exceptions and I should see if I can track this down at the same time.  
> I suspect it's related, or at least in the same code areas.
> 
> David
> 
> Mike Matrigali (JIRA) wrote:
> 
>>     [ http://issues.apache.org/jira/browse/DERBY-159?page=all ]
>>
>> Mike Matrigali updated DERBY-159:
>> ---------------------------------
>>
>>      Component: Network Server
>>    Description: A simple code below will demonstrate that warnings 
>> generated by Derby running in Server mode do not make their way to 
>> client. The client code below is trying to create the database db1drda 
>> which already exsits. Server generates a warning for that but the 
>> client cde below does not print it.
>>
>> con = 
>> DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true;",

>> "app", "app");
>> SQLWarning warnings1 = con.getWarnings();
>> System.out.println("database exists, should get warning");
>> while (warnings1 != null)
>> {
>>     System.out.println("warnings on connection = " + warnings1);
>>     warnings1 = warnings1.getNextWarning();
>> }
>>
>>
>>
>>  was:
>> A simple code below will demonstrate that warnings generated by Derby 
>> running in Server mode do not make their way to client. The client 
>> code below is trying to create the database db1drda which already 
>> exsits. Server generates a warning for that but the client cde below 
>> does not print it.
>>
>> con = 
>> DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true;",

>> "app", "app");
>> SQLWarning warnings1 = con.getWarnings();
>> System.out.println("database exists, should get warning");
>> while (warnings1 != null)
>> {
>>     System.out.println("warnings on connection = " + warnings1);
>>     warnings1 = warnings1.getNextWarning();
>> }
>>
>>
>>
>>    Environment:
>>  
>>
>>> When Derby runs in Network Server mode, client does not receive 
>>> warnings generated by Derby
>>> -------------------------------------------------------------------------------------------

>>>
>>>
>>>         Key: DERBY-159
>>>         URL: http://issues.apache.org/jira/browse/DERBY-159
>>>     Project: Derby
>>>        Type: Bug
>>>  Components: Network Server
>>>    Reporter: Mamta A. Satoor
>>>   
>>
>>
>>  
>>
>>> A simple code below will demonstrate that warnings generated by Derby 
>>> running in Server mode do not make their way to client. The client 
>>> code below is trying to create the database db1drda which already 
>>> exsits. Server generates a warning for that but the client cde below 
>>> does not print it.
>>> con = 
>>> DriverManager.getConnection("jdbc:derby:net://localhost:1527/db1drda;create=true:retrieveMessagesFromServerOnGetMessage=true;",

>>> "app", "app");
>>> SQLWarning warnings1 = con.getWarnings();
>>> System.out.println("database exists, should get warning");
>>> while (warnings1 != null)
>>> {
>>>     System.out.println("warnings on connection = " + warnings1);
>>>     warnings1 = warnings1.getNextWarning();
>>> }
>>>   
>>
>>
>>  
>>


Mime
View raw message