3) Please attach a small example of such dump (SMALL and zipped, please!). It is better to do things than to talk about things!
4) “does sqlyog check which charset the .sql-import-files have?”
both yes and no!
as regards yes YES: we detect the encoding of the file.
as regards NO: SQL imports are started in a seperate connection thread. Unlike for the GUI thread we do not SET NAMES for batch jobs, The script it self is supposed to! Does the script contain the statement “SET NAMES UT8” ?
We were able to reproduce this. We have changed a little in the code and it does not happen for us now.
What happend was that we failed to handle the REAL error occurring (“2003, Cant Connect”) properly in that particular situation and then the “error 0” would come instead.
Please check this on your machine when 6.5 RC is out.
We were able to reproduce this. We have changed a little in the code and it does not happen for us now.
What happend was that we failed to handle the REAL error occurring (“2003, Cant Connect”) properly in that particular situation and then the “error 0” would come instead.
Please check this on your machine when 6.5 RC is out.
right-click a table in the Object Browser and do either of those
>> change table type
>> .. ALTER TABLE .. advanced properties .. select InnoDB for 'table type' .. OK .. press ALTER
2)
this (default table type) is a server setting, not a client setting.
For recent MySQL version (4.1+) insert this line in the [mysqld] section of the MySQL configuration file (my.ini/my.cnf)
default-storage-engine=INNODB
.. and restart the server. If you do not have access to server configuration (a shared server) you will have to create every new table as InnoDB (or change after creation).
If you are using MySQL 4.0 or 3.x I do not remember the exact configuration parameter .. but I will be able to find out!
However, I have experienced myself an ISP who has disabled INNODB support using some 'dirty hack' when compiling MySQL and where 'have_innodb' variable still reports YES. SQLyog cannot detect this (no client can), and you will probably either have an error or (worse) no error is returned but it has no effect! Go to OBJECTS tab, scroll down and verify the CREATE STETEMENT for the table.
… but I think that the error “query support not avail” means that it was not possible to retrieve data for a “stored query” (or a VIEW if you like). VIEWs fromcan be imported to a table on . But if the driver fails to retrieve the data I think this error occurs. I have done that with Access2000 without problems however, but there might be problems with some specific “stored queries”. Or maybe JET version on that system was not able to handle that file?