[Ritesh]

We are trying to correctly figure out the consequences/implementation difference between various TEMP_STORE options in SQLite.

If both have their own advantages/disadvantages, we will probably put this as a Preference option but till now this MACHINE-GUN sound problem has only been reported by you.

[Ritesh]

powellbound wrote on Feb 21 2006, 07:08 PM:

Hi all,

---

SQLyog Enterprise – MySQL GUI

---

Error No. 2008

MySQL client run out of memory

---

OK  Help 

---

[post=”8828″]<{POST_SNAPBACK}>[/post]

Since you are using HTTP tunneling, the client at the PHP is breaking. Your problem is same as:

http://www.vbulletin.com/forum/archive/ind…hp/t-16473.html

BTW, starting with v5.1 BETA 1, SQLyog will get the data in blocks of 100 rows which will by-pass the resource limit put by your ISP.

v5.1 BETA 1 can be downloaded at: http://www.webyog.com/forums/index.php?sho…view=getnewpost

Just try v5.1 BETA 1 once and let me know how it goes.

[Ritesh]

A user can add Favorite linked to a file. In that case he doesn't need to add a query in the editor.

I think we should keep the menu option enabled to allow a user to add a reference to a SQL file to the favorite without writing some characters in the query editor.

[Ritesh]

Add to Favorites will be enabled only when there is some query in the editor. There is nothing to ADD if the query window is empty.

[Ritesh]

I think the option to do case-sensitive or case-insensitive checking should be put into preference.

The data-sync as well as structure-sync were case-sensitive in the earlier versions and due to couple of user-requests, we made it case insensitive.

[Ritesh]

uyuni wrote on Feb 21 2006, 11:29 PM:

It would be a nice feature to download and sync tables from a MySQL source to Access (or a different ODBC source). Is this planned?

[post=”8838″]<{POST_SNAPBACK}>[/post]

You can already sync an ODBC database to MySQL using the TRIGGERS option of Migration Toolkit.

We dont have any plan as of now for a feature to download and sync tables from a MySQL source to Access.

[Ritesh]

Can you tell me an instance of some work that you were doing and SQLyog crashed?

[Ritesh]

What if a USER actually wants to enter a blank string and not NULL. We cannot differentiate in that case.

By default, SQLyog shows the default value in the grid. From v5.1 BETA 2, it will show the string (NULL) which SQLyog interprets as NULL.

We plan to keep BLANK cell as '' and if somebody specifically wants to insert a NULL value, he will need to write (NULL).

For a column having auto_increment value, SQLyog will insert '' if left blank and the server correctly handles it by inserting the next auto-increment value in the field. This works for MySQL versions 3.23.x to 5.x.

[Ritesh]

I just checked with 1500 tables in our local network and here are the statistics:

1) Direct connection: It takes less than 3 seconds.

2) HTTP Tunneling: It takes less than 10 seconds.

There will always be a slight difference in speed between Direct connection and HTTP Tunneling.

[Ritesh]

5.1.7 implementation has two known bugs which will not be fixed in 5.1.7 as the MySQL developers have shifted to 5.1.8 tree.

We will implement this feature in SQLyog as soon as an alpha release of 5.1.8 is released.

[Ritesh]

This is VERY VERY strange!

SQLyog is supposed to be several times faster that any of the competing products.

I need some information about your configuration:

1) Are you using HTTP tunnelling while connecting from SQLyog?

2) Can you cut-n-paste the SQL commands from the History tab after expanding the database? If you dont want them to be displayed at the public forums, please send a mail to [email protected] specifying your order no.

Last but not the least, dont worry about your purchase. After helping us pin-point the exact problem, if you dont find SQLyog to be “several” times faster than any of the competing products, you can claim a full refund. No questions asked!

[Ritesh]

lazylester wrote on Feb 10 2006, 01:56 AM:

Hard to believe, but this:

You got a PM!

[Ritesh]

Structure Sync is case insensitive.

I have to put this for v5.1. We will fix this along with COLUMN ORDER issue in structure sync.

[Ritesh]

Yes indeed it should be a PLUS. Your log also confirms that there is a space so I guess there is an error in that.

I will now work on this to see if there is a bug in our BASE64Encoder implementation.

The strange part is that it works on our local PHP as well as PHP system hosted at our webserver.

[Ritesh]

From SQLyogTunnel.php:

Code:

   /* fix in v4.1 that checks for global configuration flag get_magic_quotes_gpc() to stripslashes or not */
   /* fix in 4.2. We have to use rawurldecode instead of urldecode. Urldecode converts + to space which is wrong */  
   if (get_magic_quotes_gpc()) {
       $xmlrecvd = stripslashes ( rawurldecode ( $_POST['textfield'] ) );
   } else {
       $xmlrecvd = rawurldecode ( $_POST['textfield'] );
   }    

I think that holds the key.

Also what happens in your server if you just do base64_decode(…) of:

Code:

aW5zZXJ0IGludG8gcHJvZHVjdHMgdmFsdWVzKDExLA0KJ1ByYWdtYXRpYyBVbml0IFRlc3RpbmcnLA0K
1xyXG48L3A JywNCicvaW1hZ2VzL3NrX3V0Y19zbWFsbC5qcGcnLA0KJzI5Ljk1JywNCicyMDA0LTA2LTE4IDAwOjAw
jAwJyk=

No stripslashes, no htmlentities.

[Author]

Posts