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.
To reproduce, try and load the last bit of the Sakila database, which has a bunch of multibyte strings. This fails with the JDBC error "Error code 0, SQL state null: Not a valid escape sequence". This is because the JDBC driver is trying to parse the SQL for escape sequences, and it bangs into multibyte strings. You can turn off escape processing in JDBC using the method See http://bugs.mysql.com/bug.php?id=4279 and http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/statement.html (look for "5.1.6 SQL Escape Syntax in Statements"). Also see http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Statement.html#setEscapeProcessing(boolean). Note that this has no effect for PreparedStatements, so you have to use regular statements if you want to avoid escape processing. One solution would be to let the user toggle escape processing for a given connection.
David, since sakila plugin is ready I think we can consider this issue as FIXED. Right?
This was a red herring - it wasn't multibyte -- it was raw binary data for a PNG file. This raw binary data (not encoded as a MIME type or anything) contained 'quotes'; there is very little we can do about this. Loading raw binary data through the SQL editor is not supported.