[Sibin A S]

Hello,

 

Currently SQLyog does not support foreign keys for the NDBCLUSTER storage engine.

 

As MySQL Cluster v7.3+ supports foreign keys for NDBCLUSTER storage engine, we have added your request in our issue tracker, here >> https://github.com/webyog/sqlyog-community/issues/2113. 

 

Regards,

Sibin

[Sibin A S]

Hi John,

 

Supporting JSON is definitely something that we want to do, but realistically it will take no less than around 6 months to provide full support. One reason is that the JSON datatype isn’t supported in MariaDB yet. However from the MariaDB mailing list we understand that this is planed for MariaDB 10.2, which can also be referred here >>  https://mariadb.com/kb/en/mariadb/plans-for-10x/ . We want to wait for their implementation as our (client side) implementation should support both ideally with the same code.

 

Regards,

Sibin

[Sibin A S]

Hi,

 

It is only possible to execute import from an external source one at a time. You may also refer how to copy the tables using incremental import sessions. For more information, please refer our doc >> http://sqlyogkb.webyog.com/article/283-copy-tables-from-the-data-source-incremental-import-sessions

 

You can use the ‘Save & Schedule it using Windows scheduler’ option to schedule the import to be executed at any particular time. For more information, please refer our doc, here >> http://sqlyogkb.webyog.com/article/285-job-use-choices

 

Regards,

Sibin

[Sibin A S]

Hi,

 

Please read our FAQ regarding this error, here >> http://faq.webyog.com/content/23/15/en/error-no-2003-can_t-connect.html

 

Also please try to temporarily disable the firewall on the machine where it does not work in order to see if it is a local firewall issue. And also double-check the spelling of the hostname and the port.

 

You may also refer the mysql documentation here >> http://dev.mysql.com/doc/refman/5.7/en/can-not-connect-to-server.html

 

Regards,

Sibin

[Sibin A S]

Hi,

 

This issue has been fixed in SQLyog v12.2.4. You may also refer the release notes from our blog, here >> http://blog.webyog.com/2016/05/27/sqlyog-mysql-gui-12-2-4-released/

 

Regards,

Sibin

[Sibin A S]

Hi Larsen,

 

You can post any of your feature requests in the forum as we always keep tabs on forum requests or you can write a email to us at [email protected]

 

Regards,

Sibin

[Sibin A S]

Hi,

 

We have fixed this issue in SQLyog 12.2.3. 

 

You can refer the release notes, here >> http://blog.webyog.com/2016/05/26/sqlyog-mysql-gui-12-2-3-released/

[Sibin A S]

Hello Larsen,

 

Can you please attach the screenshots of the same.

[Sibin A S]

Hello Larsen,

 

Can you please clarify a bit more by elaborating on,

 

• Whether the database was created using SQLyog?
• Do you find the database listed under the specific user it was created ?

 

To view objects on which the user has privileges, check “Show only privileged objects” at the bottom left corner of the ‘User Manager’ dialog. 

 

After checking the checkbox, do you find the object to which the user has privileges in the list?

 

Regards,

Sibin

[Sibin A S]

Hello Larsen,

 

We have added you request in our issue tracker, here >> https://github.com/webyog/sqlyog-community/issues/2109

 

Regards,

Sibin

[Sibin A S]

Hello,

 

We have added your request in our issue tracker, here >> https://github.com/webyog/sqlyog-community/issues/2107 . The priority is not decided though.

 

Regards,

Sibin

[Sibin A S]

Hello Mirlynn,

 

Can you please tell us your SQLyog version? We have fixed an issue regarding memory leak as well as a crash in Session restore when writing a restore point in SQLyog v12.17. 

 

The session details are stored in the “connrestore.db” file.  Please note, by clearing the session details, you will loose all the unsaved data. You can clear the session details by deleting the file “connrestore.db” from the filepath “C:UsersAppDataRoamingSQLyog“.

[Sibin A S]

This issue has been fixed in the SQLyog 11.26 version. Please refer >> http://blog.webyog.com/2013/10/11/sqlyog-mysql-gui-11-26-released/

[Sibin A S]

Hi,

 

We have been successful in finding where the issue lies and it seems to be a bug in the code. We will be fixing this in the next release as soon as possible and will update you on this.

[Sibin A S]

Hi,

 

We appreciate the time you have taken in elaborating the test-case. We did try the test-case that you mentioned and were successful in reproducing it our end. We will surely look into this issue and update you with the progress. Thanks in advance for your patience.

[Author]

Posts