[vishal.pr]

@Jason O'neil

ALT + Selection is used to make rectangular selection and its a Scintilla property, the editor component used in SQLyog. The behavior you mentioned is verified and will be reported to Scintilla developers. If it is confirmed as bug we may provide a fix for this. However, you can try the reverse here. That is, start the selection from top right and extend it to left. this will work.

Regards,

Vishal P.R

[vishal.pr]

@arkid77

Quote:

The most confusing part is that the drop down lists in the map page didnt even include the columns in my underlying database due to them not matching the exact same len value as the source.

This was a bug in SQLyog prior to version 9.1 and has no relation to length of the table, in fact SQLyog never considered the length or other properties of a column to list it in the target column field. This bug was fixed in SQLyog 9.1, the release notes says

Import External Data could fail to display all columns of target table when importing from a source containing lesser columns than target.

Please refer to

http://www.webyog.com/blog/2011/06/09/mysql-data-search-data-at-your-finger-tips/

But as you said there may be room for improvement in the current interface if the user selected import into existing table and we already started discussing this. I will update you the status once the decision is made.

Regards,

Vishal P.R

[vishal.pr]

@arkid77

The mapping section will always show the column length and other properties of the column given in the source no matter whether you have selected to import into an existing table. Importing into existing table will never modify the target table structure even though mapping section shows otherwise, these values will have effect only if you drop and recreate the table.

FYI: Import into existing table is controlled by the DDL/DML Optionsin the Advanced Options.

Regards,

Vishal P.R

[vishal.pr]

Hi,

SQLyog uses PuTTY Private Key Files (ppk format) for public/private key authentication. So, please make sure that the key file you are using is in ppk format. If you are using ppk format and still getting the error, make sure your pass-phrase is correct. You can try the same with PuTTY(http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html).

If you are using OpenSSH keys, refer the following link to convert them into ppk format

http://meinit.nl/using-your-openssh-private-key-in-putty

Also please visit the below SQLyog FAQ link for common SSH error messages.

http://webyog.com/faq/content/22/113/en/ssh-error-messages.html

Regards,

Vishal P.R

[vishal.pr]

@DAE51D

This is how merge tools shows the difference. If an object is there in the source and not in the target, source should be indicated with the absence of the object (with gray color) and target with the presence of the object (with green color). Thus, the object with gray color is the one to be dropped in the target 🙂

Regards,

Vishal PR

[vishal.pr]

Just a point to add to my previous post. I think the original table/column name make sense only when you are exporting the result set as SQL. So it can be a user configurable option (a check box for instance) to use original table name that should be grayed out in case of HTTP connection.

[vishal.pr]

This is confirmed to be a bug since MySQL result structure does avail the original table name under org_table. However this is not possible through HTTP connection as PHP does not expose such information. Same with aliases for column name.

The issue reported here.

http://code.google.com/p/sqlyog/issues/detail?id=1655

We will check this with priority. Thank you for reporting the issue.

Regards,

Vishal P.R

[vishal.pr]

These issues were fixed in SQLyog version 8.7

Refer to:

http://www.webyog.com/blog/2010/11/19/sqlyog-mysql-gui-8-7-released-form-view-improved-sql-formatter-and-more/

The Query Formatter is now completely rewritten. In principle all types of SQL statements are now supported and all limitations with the old implementation are lifted.

Regards,

Vishal P.R

[vishal.pr]

Issue reproduced as described and is fixed now. Now if the the mouse wheel happens inside the list window it will scroll the list contents otherwise the grid.

The fix will be available in next public release. Thank you for reporting the issue.

Regards,

Vishal P.R

[vishal.pr]

Can you execute the following query in your environment and see how much time it is taking?

Code:

SELECT
`TAGNAME`,
`DATATIME`,
`VALUE`,
`EXPIRY`,
`LASTFETCHED`,
`ERROR_DESC`,
`QUALITY`,
`WWRESOLUTION`,
`WWRETRIEVALMODE`,
MD5(
CONCAT_WS('#', `TAGNAME`, `DATATIME`)
) AS __crc
FROM
`tag_data5mins`
WHERE (1 = 1)
AND (TO_DAYS(NOW()) – TO_DAYS(DATATIME) <= 1)
ORDER BY `TAGNAME` ASC,
`DATATIME` ASC;

**Query formatted using SQLyog SQL Formatter.

Regards,

Vishal PR

[vishal.pr]

production.table

id(PK)

---

1

2

3

4

5

backup.table

id(PK)

---

6

7

8

Now once the problem is solved you switched back to production db, so the current state of production.table became

production.table

id(PK)

---

1

2

3

4

5

6

7

8

Am I correct?

[vishal.pr]

Hi Rich,

Please tell what all columns from the table `tag_data5mins` is used in the Columns to Compare option. Also the exact where clause you supplied in the SQL Where (nothing more, nothing less). Once you provide these details we can frame a query that gets the rows to sync and you can execute the same in your environment to see how much time it takes. We can then help you to optimize the WHERE clause used.

Regards,

Vishal PR

[vishal.pr]

Please goto Tools->Preferences and under General preferences uncheck the option Generate queries using backquote(`)

Regards,

Vishal P.R

[vishal.pr]

Hi ruirib,

Thank you so much for bringing this to our notice. We've already changed this and starting from next public release the executables will have proper version number.

Regards,

Vishal P.R

[vishal.pr]

Its because SET FOREIGN_KEY_CHECKS = 0;

Read this http://dev.mysql.com/doc/refman/5.5/en/innodb-foreign-key-constraints.html

[Author]

Posts