[peterlaursen]

Still discussing scenario#2:

You can open the 'edit sql' display. If you close it by clicking 'Cancel' or 'X' you will not get this error, you only get it when closing the dialogue by clicking 'OK'.

The idea was originally that it should be possible to edit the query. If 'OK' is used it is assumed that it was edited and we check for every column in the source.

I think we have do realize that this is not a well designed GUI here .. most users will assume that 'OK' means 'thats fine – proceed' and 'Cancel' means 'stop – I dont want this job to run. But the meaning is to approve/disapprove the changes made to the query! But I can see now that that is not very clear. Also we should make this dialogue non-editable I think!

[peterlaursen]

as regards scenario #2:

Can you confirm that it does not throw that error if you don't click on 'edit sql' before executing?

[peterlaursen]

I am sorry, we have fixed in the trunk but did not finish testing.

A 'workaround' for this is to execute the SQL script from Structure Sync in a 'advanced' query tab. The 'advanced' query tab is the one that opens the templates for generating Stored Procedures etc.

From the database menu .. create store procedure ..give a dummy name .. delete the template .. and paste the STRUCT SYNC SQL instead .. execute all.

[peterlaursen]

you can manually issue a SQL command like

UPDATE table SET …. WHERE … LIMIT x.

(x is a number – '1' for instance)

But better you should have a Primary key in the table and include that PK column in the SELECT that opens a RESULT tab

[peterlaursen]

“and SQLyog has always worked perfectly.”

If so something must have changed on the server! I think only the helpdesk could tell what it is. The privileges system on sahred hosting can be a little complicated – because not only MySQL privileges are involved but also OS/file system privileges

[peterlaursen]

Let me add that if you use 'shared hosting' you may not be able to use SQLyog for user/privileges management.

It is common with shared hosting that users can only be managed from the webbased admin panel available.

[peterlaursen]

Both yes and no.

We know and understand the problem, but solution is not implemented. This is scheduled for version 6.2

[peterlaursen]

we just did a brief test.

We cannot reproduce (MySQL 5.0.41) .. or we do not understand what you are telling. So please detail!

(screenshots are always good for illustration of such issues)

[peterlaursen]

I doubt this happens when RESTORING – rather when EXPORTING.

Could you open the dump in an editor and check this, please?

How was the dump created? SQLyog export, SQLyog scheduled backup or by some other program?

This is probably not important but you should always tell the MySQL version!

And it would be a little help if you pasted in a small example!

[peterlaursen]

We will try to fix this VERY soon and give you a private build with the fix for this.

VERY SOON may mean today itself or tomorrow.

[peterlaursen]

“…and check the database that i created the view in, i don't see the view in the list of tables”

You should absolutely see the VIEW itself in the database where it belongs! (and if you do not understand Information_Schema then keep your hands off it!)

What is the SQLyog version you are using? Is it recent? Please try a recent version if you don't!

[peterlaursen]

hmmmm … this looks very well tested and documented already.

Those issues here are all GUI issues and not related to DATA. Also it would not matter ifis Oracle or MySQL or whatever.

We will research it in details tomorrow!

[peterlaursen]

Please ALWAYS tell the SQLyog program version you are using!

If it is not recent, then first try an upgrade.

I think I recall such issue was fixed 3-6 months ago.

And if it is reproducable with a recent version we need a test case to reproduce with!

[peterlaursen]

Please confirm that you can connect to the tunneller from a browser!

If possible we would very much like to connect from inside of debugging environment for solving this.

We don't need any data. You can create a empty database and a new user. Grant this user all privileges to that database only.

You can create a ticket and leave details (user, password, URL to tunneller) there.

[peterlaursen]

I apologize for a stupid question. With COMMUNITY you are using direct connection!

The error is a mysql (API) client error.

We would very much appreciate if you could give some more details so that we can fix this issue as fast as possible.

Could you pleae

1) tell what server versions you are using?

2) attach a structure-only dump of that database (you can create a ticket if you want privacy)

[Author]

Posts