Bug #77394 When warning count is 0, Statement/Connection.getWarnings() should be a no-op
Submitted: 17 Jun 2015 17:54 Modified: 24 Jan 2022 12:27
Reporter: Mark Matthews Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:5.1.35 OS:Any
Assigned to: CPU Architecture:Any

Contributions can be accepted to Open bugs only.