[vishal.pr]

Hi,

We recently updated the Scintilla library used in SQLyog. With this some of the macros used in old version is no longer the same and many of the source files for Scintilla control are now redundant. So I would recommend you to do a fresh checkout and try.

Regards,

Vishal P.R

[vishal.pr]

Hi,

I guess there is no way. information_schema is a virtual database that provides meta data. It contains information about the databases managed by the server, but it should only show information about those databases and database objects that are accessible to the current user. So I don't think there is any problem exposing this to the user.

Regards,

Vishal P.R

[vishal.pr]

Hi,

Issue confirmed. With large number of rows grid operations are not proper. The issue is fixed now and will be available in next public release.

Thank you for reporting.

Regards,

Vishal P.R

[vishal.pr]

Lars,

That was a choice between consistency and relevance, because the button text changes depending on the context user is working on. i.e the button text will change from Save Changes to Create when you switch to create user page (and you can see e is common in both 😉 ). But while checking this we found a bug that the button text will change to Save Changes once you create a user. Its fixed now and the accelerator is changed as you suggested. The fix will be available in the next public release. Thank you for pointing out the issue.

Regards,

Vishal P.R

[vishal.pr]

Hi,

We have tried to fix these issues

You can download the special (not-release) SQLyog build from here:

http://webyog.com/downloads/betas/not_released/SQLyog-8.62n3-Community.exe

Please try this special build in your environment and let us know the status.

Thank you

Vishal P.R

[vishal.pr]

Hi Brian,

Its not SQLyog that revokes the privileges, but it is MySQL server that revokes the privileges.

Please refer to http://dev.mysql.com/doc/refman/5.0/en/alter-procedure.html

Which says, You cannot change the parameters or body of a stored procedure using ALTER PROCEDURE statement; to make such changes, you must drop and re-create the procedure using DROP PROCEDURE and CREATE PROCEDURE.

Now refer to http://dev.mysql.com/doc/refman/5.0/en/grant.html

which says, MySQL does not automatically revoke any privileges when you drop a database or table. However, if you drop a routine, any routine-level privileges granted for that routine are revoked.

I hope that explains what is happening in your case. Since ALTER PROCEDURE statement cannot be used to alter the SP parameter/body, SQLyog generates statements to drop and recreate the SP. And on dropping the SP MySQL revokes any privilege applied on that.

However, we had a similar report in the past asking for SQLyog to generate the necessary statements to retain the privileges while altering a stored procedure and it is recorded in our issue tracker.

Please refer to http://code.google.com/p/sqlyog/issues/detail?id=1438

Currently the priority is not set, but let us discuss this in the next team meeting.

Thank you.

Vishal P.R

[vishal.pr]

Hi,

Parenthesis highlighting inside “double quoted string”, 'single quoted string' and `quoted identifier` is disabled now and will be available in the next release.

Regards,

Vishal

[vishal.pr]

Hi,

The issue has been added to our issue tracker.

Please refer to http://code.google.com/p/sqlyog/issues/detail?id=1443

Thank you for reporting.

Regards,

Vishal P.R

[vishal.pr]

Hi,

Request added to our issue tracker.

Refer to http://code.google.com/p/sqlyog/issues/detail?id=1438

Regards,

Vishal P.R

[vishal.pr]

Hi,

We understood your requirement. Currently there is no way you can do this with SQLyog. Why because, there may be many users having privileges on the same SP. Then while altering we many need to generate/execute the grant statements for all those users also, which is not safe and can fail if the user trying to alter the SP don't have GRANT privilege.

Thank you,

Vishal P.R

[vishal.pr]

Hi,

The Scintilla control will style the characters based on the style we give (http://www.scintilla.org/ScintillaDoc.html#Styling). Normally this is done by writing a lexer for the language of choice and then setting the lexer language (http://www.scintilla.org/ScintillaDoc.html#Lexer). The Scintilla version SQLyog uses is 1.72 and thus it uses a different MySQL lexer as compared to the version 2.22. You can check the LexMySQL.cxx and LexMySQL.h for details. Also please take a look at http://www.scintilla.org/Lexer.txt to know more about how to write a lexer.

Regards,

Vishal

[vishal.pr]

Hi Dan,

We have released 8.6 Beta1 with new User Manager interface.

Please refer to:

http://www.webyog.com/blog/2010/07/20/sqlyog-mysql-gui-8-6-beta1-released/

Regards,

Vishal P.R

[vishal.pr]

Hi Kevin,

We have released SQLyog 8.5 Beta2 with this feature. Now Keyboard shortcut F3 will find the “Next match” in Query Editor if a search string is already there, otherwise it will open the default find dialog.

Please refer to

http://www.webyog.com/blog/2010/05/18/sqlyog-mysql-gui-8-5-beta-2-released/

Regards,

Vishal

[vishal.pr]

Hi,

We have released SQLyog 8.5 Beta2 with this feature. Now Keyboard shortcut F3 will find the “Next match” in Query Editor if a search string is already there, otherwise it will open the default find dialog.

Please refer to

http://www.webyog.com/blog/2010/05/18/sqlyog-mysql-gui-8-5-beta-2-released/

Regards,

Vishal

[Author]

Posts