dbForge for MySQL (Pro) 6.3.358 is corrupting data

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
gr8kodr
Posts: 4
Joined: Thu 12 Mar 2015 17:44

dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by gr8kodr » Tue 04 Aug 2015 04:17

dbForge for MySQL (Pro) 6.3.358 is corrupting data when opening UTF-8 encoded files.

I need the UTF-8 encoding because the dataset I'm trying to save contains Japanese text.

additionally, when finalised the data will be ported to a UNIX server, so the input file is encoded with UNIX style line endings.

I was able to import the data to my table using MySQL Workbench, but I would like to know how to enable dbForge to handle the initial SQL insert script without munging the entry values.

Once the data exists, I can export it without any problem ... most perplexing

alexa

Re: dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by alexa » Tue 04 Aug 2015 09:50

Please try selecting 'utf8 -> Unicode (UTF-8)' on the 'Advanced' tab of the 'Database Connection Properties' dialog box that can be opened by right-clicking the connection in Database Explorer and selecting 'Modify Connection' from the popup menu.

gr8kodr
Posts: 4
Joined: Thu 12 Mar 2015 17:44

Re: dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by gr8kodr » Tue 04 Aug 2015 12:19

I have that set by default

the problem isn't with the data read (out), it's the script read (in) .... when I open a script to add data to my table, all the Japanese is getting corrupted

ironically, if I go back to my text editor and copy the script in it's entirety and paste it (as opposed to opening the file directly) into a SQL script within Studio, the Japanese text all appears normal

alexa

Re: dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by alexa » Tue 04 Aug 2015 12:39

When opening a file in dbForge by selecting 'File -> Open File...' in the main menu, you can select the encoding in the 'Encoding' drop-down menu of the 'Open File' dialog. Please let us know if that solves the issue.

gr8kodr
Posts: 4
Joined: Thu 12 Mar 2015 17:44

Re: dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by gr8kodr » Tue 04 Aug 2015 21:42

Thanks alexa, that solved it :D

is there a way to tell the IDE that my default file encoding is UTF-8 (65001) so I don't always need to change the selector from Western European?

alexa

Re: dbForge for MySQL (Pro) 6.3.358 is corrupting data

Post by alexa » Wed 05 Aug 2015 09:55

Thank you for the reply.

Unfortunately, there is no such a possibility. However, you can add a suggestion on our UserVoice forum where other users can vote for it http://devart.uservoice.com/forums/7729 ... -for-mysql

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

Post Reply