[peterlaursen]

@Gareth

“It is just strange

that it doesnt work all of a sudden…”

Also you should tell from what version you upgraded!

For you it seems to be another issue. We will need remote access to your server if we shall work with it.

You can:

* create an empty database and a new user that have all privileges (except DROP and GRANT) to that database only (this will ensure that we cannot access your data, what we basically do not want to do!)

* create a ticket to inform about connection details-

[peterlaursen]

We are aware of one more such situation with IIS version 6 and Windows 2003 (IIS version 5 and XP is not affected).

We believe it is an issue with the IIS/PHP interface and not SQLyog. More precisely the issue is that the web server is not accepting the header:

“Content-Type: application/x-www-form-urlencoded” from external sources. You can test this from a *nix shell (You need *nix to execute POST, but Putty will do):

$ POST [url=”http://serverURL/path_to/SQLyogTunnel.php”]http://serverURL/path_to/SQLyogTunnel.php[/url]

Please enter content (application/x-www-form-urlencoded) to be POSTed:

name=peter&

roll=123&

If you get:

500, timeout error message.

“

.. this is the problem

If it is OK you will get something like:

4not well-formed (invalid token)

Solution:

PHP for windows is available in two builds:

1) a package with an automatic installer

2) a package for manual configuration

This issue has only been seen when 1) was used. Uninstalling and using 2) instead has solved the issue.

You may use this configuration guide:

http://ourthinktank.org/?p=34

BTW: from what version did you upgrade?

[peterlaursen]

Did anybody experience this recently?

The reason that I ask is that I did not after installing a handfull of Vista updates from Windows Update about 2 weeks ago!

[peterlaursen]

Did anybody experience this recently?

The reason that I ask is that I did not after installing a handfull of Vista updates from Windows Update about 2 weeks ago!

[peterlaursen]

Thanks for trying and thanks for the information.

We will analyze on Monday.

[peterlaursen]

I never saw 'Application Data' folder localized before (like 'Data aplikací'). 'Program Files' is almost always localized, but 'Application Data' most often not (for instance not in Dansih).

I am sorry but we will only be able to check these details with the code on Monday. Until then you will have to live with it or reinstall 6.05.

But you may try if you can create the “…Application Datasqlyog” parallel to “…Data aplikacísqlyog” and copy the file.

[peterlaursen]

You are right that support for alias in autocomplete is missing. When columns and other object have 'weird' names (what is often the case with big 'live' databases) it would be very nice. You are not the first one pointing to that.

However we will then need to parse the content of the editor (in real time) to identify the alias names used in the context and probably store in a (MEMORY type would work) sqlite database.

Optimally we should only autocomplete aliases for each individual statement. So it raises some architectural issues that are not very simple!

We have allready recorded this in our TODO, but not scheduled it yet.

[peterlaursen]

please refer to:

http://webyog.com/faq/content/33/20/en/pla…-of-sqlyog.html

” … various re-designs of the Object Browser are being considered.” This includes this.

I think GUI redesign will start in the beginning of next year only. We will need around 2 month to finish what we have started and we also need to 'catch up' with recent MySQL enhancements (Events, Table Partitions) before that because MySQL 5.1 stable is planned to be released early Q1 2008.

[peterlaursen]

Did you upgrade from COMMUNITY to ENTERPRISE?

Did you install to the same folder as before?

1) If no: copy the sqlyog.ini file to the new position

old position: installation folder

new position:

2K/XP/2003: documents and settingsuserapplication datasqlyog

Vista: usersuserappdataroamingsqlyog

2) if yes: a backup of sqlyog.ini is left in installation folder. Copy to new position.

[peterlaursen]

I cannot guarantee when we will include it! I cannot decide alone. We will need to discuss. Most of our people left office now or will soon (it is 7:30 pm Indian Time on a Friday!)

I added the request here:

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

[peterlaursen]

I am sorry for not informing you!

The fix will be included in 6.1.

When we export we use utf8-encoding.

Basically we will need to specify the charset with the LOAD DATA INFILE statement to be sure that it always import correctly, no matter the server settings.

But there is an easy workaround, actually. Just open the file in Notepad .. save as .. explicitly select ANSI for the encoding. Now latin special characters will import.

[peterlaursen]

no .. this option is not there now.

I would suggest an entry in context menu 'dublicate this row' when a single checkbox is displaying whereafter a new row gets created in the grid but not saved (and the warning 'not saved' is displaying). Also autocomplete we would probably be able to handle automatically. Non-autoincrement PK's and Unique keys will have to be handled by user.

What say?

[peterlaursen]

I am almost sure I can figure the reason!

In 3.23 FLOAT(4,2) means 4 digits before and 2 after decimal sing

In 5.0 it means totally 4 digits of which 2 after decimal sign. Everything >= 100 gets truncated to 99.99

changing from FLOAT(4,2) to (6,2) before copying is probably the easiest way!

We are checking with what version it was changed. I cannot guarantee that we will fix if only 3.23 versions are affected (sooner or later we will have to say stop using efforts with rare 3.23 compability issues like this!)

[peterlaursen]

I think you can alter, the inaccuracy occurs on less significant digits.

One reason why you should avoid FLOATs is that the inaccuracy is critical for a WHERE clause

SELECT …. WHERE float = 7.32 will fail if it is internally 7.3200000000000000001 !!!

[peterlaursen]

In SQLyog the .ini file has been moved to user AppData folder:

2K/XP/2003:

documents and settingsuserapplication datasqlyog

Vista:

usersuserappdataroamingsqlyog

('users' may have a localized name)

[Author]

Posts