[peterlaursen]

Please tell with what program those files are created!

Probably the data is UTF8 encoded but the file itself is not.  

SQLyog 6.0 does both: encode data and the file tiself with utf8 – sqlyog encoded only the data in utf8 – the file itself was ANSI.  Ypou will see the same with most versions of 'mysqldump'.

Accented characters are encoded using two bytes in utf8 – only one in ANSI.

It won't change existing files to change character set settings!

What is the porblem?  Doesn't the file restore OK?  or do you want the file to be editable and readable?

Try open in Notepad –> 'save as' and select utf8 encoding for the file.  Next open again.

[peterlaursen]

also note that the FAQ was updated wil a small clarification!

[peterlaursen]

1) What is the program version you are using?

Always tell that! and please try 6.03 if you don't allready!

2) Please attach a very small SQL-file

You may need to explicitly SET NAMES in the file if it is encoded differently than the server default charset!

Refer to this FAQ http://webyog.com/faq/34_148_en.html

[peterlaursen]

my mistake

MySQL docs: http://dev.mysql.com/doc/refman/5.0/en/load-data.html

Quote:

If LOCAL is specified, the file is read by the client program on the client host and sent to the server. The file can be given as a full pathname to specify its exact location. If given as a relative pathname, the name is interpreted relative to the directory in which the client program was started.

But the point is that with HTTP tunneling LOCAL machine is the machine where the webserver/PHP is running, not your local machine.

[peterlaursen]

Yes, user should have write access to the sqlyog.ini file.

maybe we should consider storing the file in users 'application data' foler (or 'roaming' folder on Vista!)

Please tell the exact OS!  I think the default settings on 2K server and 2003 server are more restrictive that on 'non-server' windows version …

[peterlaursen]

try for yourself from SQLyog SQLpane (and read the docs again and again!).

You won't have to store any data to test this!

[peterlaursen]

Basically we know that we will soon need to focus a little more on transactions with SQLyog!

Undoubtedly MyISAM will gradually disappear and be replaced by transactional engines (innoDB, Falcon, SolidDB, Primebase).

I think that we can start working on this late summer/early autumn!

[peterlaursen]

If you are connecting to a remote server (no matter the connection method) CSV-import of a file stored locally won't work, becuase LOAD LOCAL DATA INFILE will look for the file on the computer where the server is running.

[peterlaursen]

I am using SQLyog with Vista too.

I think there is a bug in Vista, that does that if a program is started before the system has completely finished booting such crash can occur.  I have experienced this with SQLyog and other programs on Vista as well!

I also noticed that when it happens the system needs to be restarted to run that program!  Even reinstalling won't help!

Could you try please?

[peterlaursen]

“Some data that is stored in sql server as type “image” that get mapped to a longblob in MySQL is damaged. The data is a pdf file.”

Ok .. we will have to check this with the SQL server 'image' type.

Do you mean to tell that the data on SQL Server is PDF?

Will they migrate OK if stored in a SQL server 'plain' BLOB type?

please also tell:

SQLserver version?

ODBC driver version?

[peterlaursen]

I think you should devote a couple of hours to study

http://dev.mysql.com/doc/refman/5.0/en/dat…-functions.html

http://dev.mysql.com/doc/refman/5.0/en/dat…tion_get-format

mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%W %M %Y');

-> 'Saturday October 1997'

mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%H:%i:%s');

-> '22:23:00'

mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00',

'%D %y %a %d %m %b %j');

-> '4th 97 Sat 04 10 Oct 277'

mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00',

'%H %k %I %r %T %S %w');

-> '22 22 10 10:23:00 PM 22:23:00 00 6'

mysql> SELECT DATE_FORMAT('1999-01-01', '%X %V');

-> '1998 52'

mysql> SELECT DATE_FORMAT('2006-06-00', '%d');

-> '00'

[peterlaursen]

NO .. it is not like that!

You can conect to remote servers by specifying any ip (“10.0.0.125) or server-alias (“myfancyserver.biz”) also with COMMUNITY.  But you will need to use direct connection.  To use tunnelling you must use ENTERPRISE.

However CSV import uses the (My)SQL command “LOAD LOCAL DATA INFILE ….”  For that reason csv import will only work on 'localhost'. 

Also 6.x ENTERPRISE has reorganised the TUNNEL tabl into two tabs: one for HTTP another for SSH (and a SSL option was further added)

[peterlaursen]

basically (again) I think this is a server issue.  Some privilege issue in the (Linxu?) operationg system maybe.

Did you contact the support of this ISP?

[peterlaursen]

the mysql docs explains how to format.  Look in the paragraph on “DATE and TIME functions”

[peterlaursen]

“I installed 6.03, but it doesn't let me connect to remote server”

I am sorry but there is no information we can use here!

Why not?  How do you connect? What is the difference you experience between 5.19 and 6.03?

What happens – do you get some error message?

I cannot see any reason why 6.03 should behave otherwise than 5.19 in this respect!  You must explain the problem so that we can understand what is happening!

[Author]

Posts