This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | SQL Editor doesn't show warnings generated from requests | ||
---|---|---|---|
Product: | db | Reporter: | nleck <nleck> |
Component: | SQL Editor | Assignee: | Libor Fischmeistr <lfischmeistr> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 152817 |
Description
nleck
2008-02-18 06:08:34 UTC
Not a defect I think. Do you happen to know how to retrieve these warnings through JDBC (java.sql.Statement, etc.)? Thanks. This is how we do it... public SQLWarning getFirstWarning( final Statement stmt) throws Exception { SQLWarning warn; warn = stmt.getWarnings(); if( dataBase.getType().startsWith( DataBase.TYPE_MSSQL) == false) { return warn; } while( warn != null) { if( warn.getErrorCode() != 0) { return warn; } warn = warn.getNextWarning(); } return null; } Thank you. This is not hard to implement, but still it can't make into 6.5, which is feature-frozen. *** Issue 144503 has been marked as a duplicate of this issue. *** From Lance Andersen, who has also worked with Sybase via JDBC: "thanks David. both the print and raiserror are quite common in Sybase and MS SQL code/sprocs so it would be nice to support it allowing you to execute system sprocs such as sp_help correctly in netbeans." Reassigned to new owner. *** This bug has been marked as a duplicate of bug 257457 *** |