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.
When connecting to a MS Visual Foxpro ODBC data source via the JDBC-ODBC bridge the following error occurs: QUOTE Unable to obtain schema. There is insufficient information to establisch a connection to obtain list of schemas.Check database URL, user and password. Driver message: [Microsoft][OBDBC Visual Foxpro Driver] Driver not capable UNQUOTE In Netbeans versions at least up to 4.0 it was possible to continue; browse the tables and execute SQL queries. In version 5.0 the following error is given when trying to expand the tables node: QUOTE Unable to read the database structure, connection is broken; [Microsoft][ODBC Visual Foxpro Driver] Driver not capable UNQUOTE As a consequence no table information is shown, it is not possible any more to execute queries. Request: database explorer should continue to support legacy databases whose drivers have no or limited support for schema information, etc.
Looks like yet another issue caused by the fix of issue 55410.
TM 5.0 -> TBD
Can you still reproduce in 5.5? If yes, please attach a the stack trace of the exception from the message log. Thanks.
Attaching stack trace from reporter by private e-mail.
Created attachment 38647 [details] Stack trace
Thank you for the stack trace. As I expected, the driver doesn't return metadata, as seen from the second exception. What I didn't expect is that the driver even fails to return the tables, and it probably used to fail in 4.1 too, so I don't understand how it is possible that the tables were displayed in 4.1. This issue is caused by reporting any exceptions thrown by the driver instead of silently ignoring them (for which there are good reasons, for example issue 55410). I'm afraid that if the driver is so broken that it throws exceptions on such simple operations as setCatalog() and getTables(), there is nothing NetBeans can do (except for ignoring those exceptions, and I don't want to go there). On the other hand NetBeans seems to do something ugly when retrieving the metadata, as proven by issue 75595 desc 4. So I will first fix that issue and see if it also fixes this one. But if it doesn't I will probably close this issue as WONTFIX.
Making this a duplicate of 75595, since if 75595 doesn't fix this, we aren't going to fix it. *** This issue has been marked as a duplicate of 75595 ***