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 136541

Summary:	Errors when running the sakila-data.sql script
Product:	db	Reporter:	Petr Jiricka <pjiricka>
Component:	Code	Assignee:	David Vancouvering <davidvc>
Status:	RESOLVED DUPLICATE
Severity:	blocker	CC:	kaa, romanmostyka
Priority:	P2
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:
Bug Blocks:	134307
Attachments:	SQL execution log file with errors

Description Petr Jiricka 2008-06-05 10:55:00 UTC

1. Download the sakila db sample from the mysql website
2. Open both of the SQL scripts in the editor (note - you may run into issue 136539)
3. Run them against an empty database (the schema script first, obviously, then the data script)

=> There are errors when running the second script, see the attached log. Perhaps I18N issues?

Comment 1 Petr Jiricka 2008-06-05 10:56:33 UTC

Created attachment 62403 [details]
SQL execution log file with errors

Comment 2 David Vancouvering 2008-06-16 22:30:40 UTC

Looks like a real problem, but expect to fix this as part of the Sakila database work.

Comment 3 David Vancouvering 2008-07-29 00:12:42 UTC

This actually could be caused because you have not configured MySQL to support international character sets.

See http://dev.mysql.com/doc/refman/5.0/en/charset.html and http://cameronyule.com/2008/07/configuring-mysql-to-use-utf-8

Please make sure MySQL is configured correctly and try again.

Marking INCOMPLETE until I hear back whether this was the issue or not...

Comment 4 Petr Jiricka 2008-07-29 12:15:23 UTC

Ok, I'll try it out and let you know. Although, I am puzzled as to why MySQL publishes a sample database that does not
work out of the box.

Comment 5 David Vancouvering 2008-07-29 17:09:11 UTC

It probably works out of the box with the mysql command-line interface, but this uses a C-based connectivity library
rather than JDBC, and these two may behave differently with regards to how the negotiate the default character set, and
also how quoted multibyte strings are handled.

But it still could be our bug and our poor handling of multibyte strings in the editor, I just thought you might check
and see if this is the problem.

Also, I will be providing a plugin on the update center to take care of installing Sakila (Issue 134307), and I will
make sure that this works correctly. Once this is done this should no longer be an issue, you can just use the plugin.

Comment 6 John Baker 2008-08-04 20:21:29 UTC

Any chance to try this again with properly setup MySQL ?

Comment 7 David Vancouvering 2008-08-12 19:27:27 UTC

I am encountering the same issue when testing Sakila support, so when I get Sakila support in this should be fixed.

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