[Shadow]

InnoDB is enabled by default. I don't even know, whether you can disable it or not. You should check the mysql.err file (data directory) to see any error messages concerning InnoDB. But the best is to read MySql's manual about InnoDB first. A few hints:

innodb_data_file_path = ibdata1:20M:autoextend:max:1000M

innodb_data_home_dir = path

innodb_log_group_home_dir =path

innodb_log_arch_dir = path

set-variable = innodb_mirrored_log_groups=1

set-variable = innodb_log_files_in_group=3

set-variable = innodb_log_file_size=5M

set-variable = innodb_log_buffer_size=2M

innodb_flush_log_at_trx_commit=1

innodb_log_archive=0

set-variable = innodb_buffer_pool_size=10M

set-variable = innodb_additional_mem_pool_size=2M

set-variable = innodb_file_io_threads=4

set-variable = innodb_lock_wait_timeout=50

[Shadow]

Unfortunately, It's been a while since I did CSV import last. I'll do a test import tomorrow and see what I get.

[Shadow]

As far as I'm concerned, the fields' extra column is not for comments, but for displaying additional information about the given field, such as whethet it is auto increment or not. Correct me, if I'm wrong, fields cannot be commented.

[Shadow]

To change the table type right click on the table name in the object explorer and select “Change table type to” and specify the desired type. Of course, you must have correct InnoDB settings, but that's in the my.ini or my.cnf.

[Shadow]

Now, that would be great! Especially, if it were implemented as a service…

[Shadow]

As far as I can recall, warnings should appear in the messages window.

[Shadow]

Quote:

Also I note that the last field in each row has a graphical box character as the last character in the field or the only character in the field if the field was otherwise empty.

The CSV file may have a win style rn line termination, but you import the file using only n as line terminating character.

[Shadow]

Interesting, SQLyog does not seem to regard line breaks as termination of comments. Should be corrected…

[Shadow]

It's got nothing to do with SQLyog, it is all about the slappy and buggy MS ODBC driver for Excel. No matter how your worksheets are constructed, no tables will ever show up in the import wizard, you have to manually enter a valid SQL statement instead. Worksheet names must be provided as follows: [Sheet1$] (mark the $ sign!) or `Sheet1$`.

[Shadow]

Could you paste that string here with the sensitive information masked?

[Shadow]

Use the online manual with user comments because there is a comment that describes how to use a MySql db as master and slave in the same time!

[Shadow]

Yes, you should use the ODBC import wizard to get data out of excel worksheets. Unfortunately, I have never tried to import hyperlinks, but I don't think they can be imported because they are not part of the cell object's value property.

[Shadow]

I don't think you are right! It's OK to have a product name (brand name if you put it that way) and a short description of the product as it reads on webyog's index.html: SQLyog – MySQL GUI Front End.

Besides, I have had enough of products boasting with pretentious names and no valuable content…

[Shadow]

Have you checked MySql's built-in replication feature?

[Shadow]

I confirm the bug to be present in both the last RC of v3.6 and in v3.61 itself.

[Author]

Posts