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.

Bug 141739 - [65cat] MySQLSyntaxErrorException: Table 'test.test' doesn't exist
Summary: [65cat] MySQLSyntaxErrorException: Table 'test.test' doesn't exist
Status: RESOLVED DUPLICATE of bug 141210
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P2 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 23:19 UTC by sunbiz
Modified: 2008-07-29 19:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sunbiz 2008-07-25 23:19:22 UTC
[ BUILD # : 200807231346 ]
[ JDK VERSION : other ]

When trying to execute an SQL Command on a MySQL database connection,

Netbeans throws the MySQLSyntaxErrorException: Table 'test.test' 
doesn't exist. This exception is thrown when a table that does not 
exist is selected. Ideally, the SQL Command editor should be able to

detect what tables are present in the database, which we can also 
view in the Services tab under database connection.

Steps to reproduce bug:
1.) Create a connection to MySQL Server
2.) Connect to the database
3.) Right click on the connection in Services Tab and select Execute

Command
4.) Enter a select query on a table that doesn't exist (say. SELECT *

FROM test), but since test is not a table in my example table test, 
netbeans throws an exception.

NOTE: When reported using the exception reporter, it detects that it

is a duplicate of Issue #128975, but that issue is about previleges.

The entire error log can be found at:
http://statistics.netbeans.org/
analytics/detail.do?id=82262
Comment 1 David Vancouvering 2008-07-29 00:16:26 UTC
The SQL Editor is not a full SQL parser and does not check the SQL to see if things like the tables or columns exist. 
It for the most part just sends the SQL to the database and lets it report any syntax or semantic errors.

We now have code completion, so you can use that to get a drop-down of available tables and it will insert the name
correctly. 
Comment 2 David Vancouvering 2008-07-29 19:02:45 UTC
Reverting this - this *is* a problem - the issue is that it is showing up as an exception, rather than being printed to
the output window like it used to.  There is an issue I have open on this and I'll make this a duplicate.  Apologies for
misunderstanding the issue.
Comment 3 David Vancouvering 2008-07-29 19:03:38 UTC

*** This issue has been marked as a duplicate of 140068 ***
Comment 4 David Vancouvering 2008-07-29 19:05:55 UTC
Gave wrong bug id as duplicate
Comment 5 David Vancouvering 2008-07-29 19:06:44 UTC

*** This issue has been marked as a duplicate of 141210 ***