[peterlaursen]

MySQL 4.0.0. ???????????????????

if you read the error message and study the beginning of you SQL

“SELECT a.* FROM al_assets a ..”  I guess you are missing a ” . ” ??

[peterlaursen]

will the attached picture help?

source is named 'book1.csv' .  I am importing to a database where the table 'stock' already exists, and it is available in the dropdown.

'table handler' tells the table type/engine to be used in MySQL.  With existing tables it displays the type of the existing table.'

If you want to add data to an existing table be careful to select that in the 'advanced' option!

[peterlaursen]

@andy

You should absolutely not SET NAMES yourself when working with SQLyog and connected to MySQL 4.1 or higher!

Only English/ASCII characters will be treated correctly then.  You can destroy your data completely!

SQLyog 6.0 uses utf8 internally!  ONLY utf8.  No matter how data are stored!

You cannot compensate for a server bug like this!  Upgrade the server!

[peterlaursen]

Now I also tried this.

We will need to consider a columns selection.  it is not very easy to do a 'square' selection in text-mode in RESULT tab.  

Basically we like the idea.  

But we will need to finish what we have started before giving priority to this r

quest and considering possible implementations. 

[peterlaursen]

Thanks for your report.  We will now go ahead and release beta2 officially!

That will be tomorrow probably!

[peterlaursen]

but I do not understand “I note that the original case of the table columns is preserved OK.”

Please try to create a table like `MYTABLE`.  Does it become `mytable`or not if you 'refresh' the Object Browser?

If you are reporting aan issue with SQLyog (`MYTABLE` dumped as `mytable`), then please (always) tell the program version and explain detailed how to reproduce!  It is 'rather annoying' when people don't! 😛

[peterlaursen]

It is MySQL that has this (default) behaviour on Windows!  It is NOT SQLyog that changes the lettercase.

In MySQL configuration (my.ini/my/cnf)you will have set set the variable In the [mysqld] section like

Code:

lower_case_table_names=2

 

Then (on Windows) table names will be stored with the LETTERCASE as in the SQL.

Search the MySQL documentation on 'lower_case_table_names'

There is no way for us to 'override' or change the setting.  

Configuration demands access to the configuration file.

SQLyog connects to MySQL only and does not have access to the file system on the host!

[peterlaursen]

It is not SQLyog that sends this error messsage.  It is MySQL that does!

There is no (My)SQL “DECLARE” statement.

However you can DECLARE inside (BEGIN .. END) of a Stored procedure or Function (or Trigger or Event etc).

an example:

Code:

DELIMITER $$

DROP FUNCTION IF EXISTS `test`.`qs`$$

CREATE FUNCTION `test`.`qs`() RETURNS varchar(50)
BEGIN
declare querystr varchar(50);
— more operations here
return querystr;
END$$

DELIMITER;

You can also use 'user variables' like

SET @querystr = 'something'.

(and the type of a user variable is not declared)

[peterlaursen]

You shall not rename the file. The driver only recognizes certain file types! 

From inside the Migration Wizard you 'map' the source 'data.csv' to target 'data'

[peterlaursen]

We know there still is an issue in 5.03 beta1. That was also listed as a 'known issue' in the release notes.

Please try the latest non-released build (version no. “5.03 beta2n” – n means 'nonreleased build')

links:

1 community link : http://www.webyog.com/downloads/betas/not_…d/SQLyog603.exe

2 trial link : http://www.webyog.com/downloads/betas/not_…603EntTrial.exe

3 enterprise link : http://www.webyog.com/downloads/betas/not_…QLyog603Ent.exe

[peterlaursen]

What you are doing is basically correct.

I think the issue is that the MySQL version you are using will not allow for ” . ” in table names (like “data.csv”).  Only the most recent versions do.  Try change from “data.csv” to “data”.

If not solved with this then please attach a sample .csv file to reproduce with!

[peterlaursen]

No, it is not SQLyog-specific.  It is a MySQL extension to standard SQL comment syntax.

read

/*!40101 … */

as

” this is a comment if the MySQL server is not version 4.1.1 or higher “

That means that mysql versions lower than 4.1.1 will treat it as a comment, versions higher will execute what is inside.

Also non-MySQL databases will treat it as a comment! It is used for 'pseudo-commenting' MySQL specific and version-specific syntax.

The ” ! ” is commonly used in C-style programming languages meaning 'NOT'

You can search the MySQL documentation for 'comments' …

[peterlaursen]

I think my colleague Adarsh did.  I shall ask him!

[peterlaursen]

I think my colleague Adarsh did.  I shall ask him!

[peterlaursen]

@chaz .. the way you are telling, nobody can understand!

what part of the program?

how to reproduce

descriptions .. screenshots?

[Author]

Posts