[Ritesh]

Quote:

Can't CHARSET set be specific for each DB, table and even column ?

And what about COLLATION with MySQL 4.1 ++

These features are planned for v4.3.

@sdozono: HTTP being stateless in nature, SQLyogTunnel.php makes a new connection using mysql_connect() everytime. It then executes the query and disconnects. I guess in tunneling, with every connection we have to execute

Code:

SET names=xxx

. This is not required in direct connection as its persistent 🙂

I have added it in the TO-DO list of v4.2. Should be an easy hack 🙂

@sdozono: Did you get my PM regarding BLOGS?

[Ritesh]

We will be supporting UNIQUE INDEX in v4.2. SJA will then follow the given sequence:

1.) If PK found, do a sync using PK.

2.) If PK is not available and UNIQUE INDEX is present, SJA will use the UNIQUE INDEX.

3.) If there are multiple UNIQUE INDEXES on a table, SJA will use the first UNIQUE INDEX.

[Ritesh]

Quote:

(I hope if there is no specific setting, SQLyog sets default charset codes..)

Currently on successful connection, SJA executes:

Code:

show variables like '%character%'

in both source and target servers. It then executes:

Code:

Set character_set_connection=charset
Set character_set_results=charset
Set character_set_client=charset

with charset being the value returned from show variables query.

[Ritesh]

Quote:

When do you envisage that this feature will be removed?

We plan to add a feature in v4.4 or v4.5 wherein you can sync two tables without PRIMARY KEY index.

Quote:

Well, however ANY sync mechanism will need to be able to UNIQUELY identify each row of data

SJA will then use UNIQUE INDEX if PRIMARY KEY index is not found. If the user does not have any UNIQUE or PRIMARY index on the table, SJA will simply drop the target table and insert all rows from source to target.

Any ideas or suggestion is highly appreciated.

[Ritesh]

Whoa! What a discussion 😛

Let me explain how the wizard works –

Let us assume that the target database is empty and there are no tables with the name as specified in the above queries. You pasted the query and press NEXT. Now to check for its validity SQLyog actually executes the query (a step to reduce newbie errors 🙂 ). Thus a CREATE TABLE statement is executed and the table is created. When you select EXECUTE JOB NOW, the CREATE TABLE statement is again executed and thus the TABLE ALREADY EXISTS error.

As for the COLUMN DUPLICATION error, it is definitely an issue with the query. You will not be able to execute it from SQL WINDOW too.

[Ritesh]

Quote:

I'm not able to edit a saved session because SQLyog keeps thinking that a table exists even though it is not listed in the Object Browser.

Can you explain this issue a little more?

I think you will need to give more info about what you are trying to do and your current setup.

[Ritesh]

Quote:

Help (Enterprise 4.1) makes several mentions of logs, but it seems they are not being written to disk. Is there a config setting to allow this (if there is I haven't found it)?

Are you talking about the contents of the HISTORY TAB?

If yes then there is no way to save it from the GUI. You will need to cut-n-paste from SQLyog to a text editor like Notepad and save it.

[Ritesh]

http://dev.mysql.com/doc/mysql/en/show-warnings.html

Looks like the query is only supported with v4.1 and above. I have put this issue in our TO-DO list. From v4.2, the button will not be shown for MySQL versions < 4.1.

[Ritesh]

BTW, table aliasing will not work with PHP tunneling as there is no way to get information about the original table using PHP-MySQL client library.

[Ritesh]

This issue is occuring due to that fact that MySQL version < 4.1 does not send information about the original table to the client (SQLyog) when aliases are used. The same query will work with v4.1 and above as they send SQLyog the correct information about the original table. For version < 4.1, you have to use query(s) without aliases.

[Ritesh]

SQLyog simply executes SHOW WARNINGS SQL query.

What happens when you execute the query from the query window?

[Ritesh]

Can you provide me a sample query?

[Ritesh]

Currently there is no global option to do that. I have added it in the TO-DO list.

BTW, is there any special reason to use tinyint instead of char(1)?

MySQL considers TINYINT as a numeric datatype whereas CHAR is a text datatype.

[Ritesh]

When you press Next, SQLyog actually executes the query to check for its validity. Just a create table statement will create the table. If you go back and come press NEXT, the query is again checked for its validity and thus the error.

Even if you just save the file as a JOB, it will throw up an error as the table was already created at the checkpoint.

[Ritesh]

It will take atleast 8-9 months for the first BETA to be released.

[Author]

Posts