MyJSQView Column Names

The summary table column names that are displayed in each tab for a table are massaged by the MyJSQLView application. All data manipulation uses the exact database table field name, but just for a more formal display the MyJSQLView application converts some characters in the column name. The rules are: Capitalizes the first letter of each field name, convert underscore, '_', to a space and then post the first letter after the underscore to uppercase. So as an example, 'bigInt_field', would be converted to 'BigInt Field'. Just remember this character formatting in the application is not translated to activity with the database, but could be confusing if you are looking at CSV, comma separated values, or SQL, structured query language, dump in comparison to what MyJSQLView is showing.

MyJSQView Updates

MyJSQLView updates need no special attention. Just install the latest release into your existing directory. The only aspect of a new release that might be of concern is obtaining new connection parameters. Each new release that supports an additional database will have an example configuration for the connection parameters of the advanced login. Likely changes will be included in the reference myjsqlview.xml file located in the installation directory. Often the Driver, Protocol, SubProtocol, and Port parameters will be different for the various database servers. Just open the reference myjsqlview.xml file and copy and paste any additional entries desired into your own working copy of the myjsqlview.xml file. The Readme or Manual will help you locate your working copy of this file.

MyJSQView Corrupt myjsqlview.xml File

MyJSQLView comes with a reference myjsqlview.xml file in the installation directory. When the application is run for the first time this file is copied to the user's home directory. All site management is saved and retrieved from this file in the user's home directory. If the file becomes corrupt no problem, just delete it. MyJSQLView will set you up again with the reference installation file. DO NOT EDIT THE REFERENCE FILE! You may also try to fix the problem in the configuration file, the file follows basic XML format. The Readme file will help you locate this file on your particular system. Additional information about this problem may be found at the project's forum:
http://sourceforge.net/forum/forum.php?thread_id=1688040&forum_id=536519

MyJSQView Fails to Start

The most probable cause of the MyJSQLView Java application's failure to start is the lack of the MySQL-Connector/J jar file being present in the JRE lib/ext directory. Please see the README file or MyJSQLView manual for further details on installation.

Startup Tip

Need additional information during the startup? On a WIN platform bring up a command prompt or on Linux/Unix a console. CD to the directory of the MyJSQLView installation and type in the command "java -jar -verbose MyJSQLView.jar -debug". This execution technique will get you all the information you will need and more to identify problems. Remember though, that on Linux/Unix system use must be within a X window environment. Use this technique also to provide the team feedback on bugs.

Still Having Problems with A Connection

MySQL and many other databases control not only the user access to specific databases, but also from which system the user may access from. Check with your system admin. of your database server to see if you particular machine has grant rights. Also MyJSQLView uses TCP/IP to communicate with the database server. Some default installations for databases disable network connections to the database. If you are having a slow connection with MyJSQLView on a newer installation of the MySQL database then check your configuration file because MySQL by default now performs a DNS lookup for hosts which will really slow things down if you are using a LAN with static IP addresses.

Need the Drop Table Statement in a Database Scheme Export?

The Edit Preferences options panel allows the inclusion of the drop table statement when exporting a Database Scheme within MyJSQLView. Select the Data | Export | SQL then activate the Table Structure checkbox.

Having Problems During SQL Import with Packet Errors?

Seen this Alert: "SQLDataDumpImportThread importSQLFile() SQLExeception: Packet for query is too large (3393745 > 1048576). You can change this value on the server by setting the max_allowed_packet variable. SQLState: S1000, VendorError:0" The Edit Preferences options panel allows the exporting of the table data in an Explicit format. Select Data | Export | SQL then activate the Explicit checkbox. The exported data will now be separated into separate SQL statements that will not in most cases exceed the server's standard packet size upon import.