blob field slow, ferefence cannot be read

[Yuri]

Dear mods,

Here are some new experiences (using SQLyog 3.7.1 )

– querying an innoDB table with 18 rows and 10 columns WITH BLOB FIELD takes one minute and 20 seconds, when hitting [enter] after selecting a table (way too long)

– After creating a reference under “manage relationships” it cannot be edited. (well that's not that annoying), but also the reference cannot be fully read when the reference's display name is longer then 328px.

[CalEvans]

Quote:

querying an innoDB table with 18 rows and 10 columns WITH BLOB FIELD  takes one minute and 20 seconds, when hitting [enter] after selecting a table (way too long)

Ok this depends.

Since we know MySQL is blindingly fast. And we know that SQLYog can keep up with MySQL then we have to look at external factors. (available bandwidth between client and server, size of rows being returned, number of rows being returned.)

So in debugging your application (because this really isn't a bug in either MySQL or SQLYog, it's just your setup) I would suggest you look into the following questions.

1: Is the server remote or local to you?

2: How long does it take to return just 1 row?

3: What's in the blob fields? (1k of text will return a whole lot faster than 1MB of MP3's.)

4: Is it necessary for the application to have access to all 18 of the BLOB fields at once? If not, try filtering your query so that you only return 1 row.

HTH,

=C=

[Yuri]

Ok, the amount of data beïng transferred is the problem.. When i select a table i automatically hit the [enter] key for viewing the data, on big tables with blob-fields this results in a very long query time / crash. Wouldn't it be a great idea to let sqlyog exclude all the blob fields from the select query when hitting [enter] while still showing the column. Just when a blob-field is clicked the select query to that field can be executed.

(or make this a option under preferences)

And what about the references that cannot be read ?

Thanks in advance…

[CalEvans]

Quote:

Wouldn't it be a great idea to let sqlyog exclude all the blob fields from the select query when hitting [enter] while still showing the column. Just when a blob-field is clicked the select query to that field can be executed.

Nope, it wouldn't. An option would be acceptable as long as it defaults to the current behavior.

One wishlist item I'd like to see is a 'Select Statement for this table' like we have for Insert. This way I can delete the fields I don't want. (Because I have the exact same problem as you do in that respect.) Currently, I'll let SQLyog give me the Insert statement and then I strip out everything and use the field names for the select statement. On my larger tables, this beats typing them by hand.

Don't know about the references. I'm not having that problem.

=C=

[Shadow]

Editing foreign key are on my wishlist, but I think Ritesh mentioned this feature as one of the enhancements in SQLyog MAX.

[Yuri]

Why not add an “update statement for this table” also ?

Quote:

Don't know about the references. I'm not having that problem.

Do you mean that the display size of the window i've added as screenshot in my first post differs from yours?

Quote:

but I think Ritesh mentioned this feature as one of the enhancements in SQLyog MAX.

Thats nice, but i feel like it should be included in SQLyog also. (guessing that the upgrade to SQLyog MAX is not free).

[Shadow]

Ritesh said he would offer MAX at a discount price to current users.

[CalEvans]

Yuri wrote on Aug 30 2004, 01:29 PM:

Quote:

Don't know about the references. I'm not having that problem.

Do you mean that the display size of the window i've added as screenshot in my first post differs from yours?

No, I just don't use that editor to edit relationships. I'm old-school if I have to change a relationship, I do it by hand.

=C=

[Shadow]

Actually, I don't use foreign key restrictions too much, I use application logic instead.

[Author]

Posts