forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Empty Text Field In Row, Shows Other Row's Content When Viewed!
- This topic is empty.
-
AuthorPosts
-
-
November 15, 2010 at 11:17 am #12155marcmMember
Ok I found a weird bug it seems.
I have a simple table with six fields. It has one text field. The other fields are just Integers and a timestamp.
The table is hosted live on my server, and I'm viewing the table with my full copy of SQLyog. It has 70k plus rows.
Tonight I noticed some of the rows do not appear to have any content in the text field. However, when I click on the row ( and text content field ) in the table data window to see the content, it is showing me content! I then searched for that exact content and found it to be in another row altogether!
When I view just that row, the empty text field row, with a select statement, the content in the text field does indeed appear empty.
For example: Row with primary ID of 71025 has an empty text field. It shows 0B. I click on it and it shows me text. I then search for that row specifically SELECT * FROM table WHERE table_id = 71025;
And it shows me the same row alone. I click on the TEXT field and it is indeed empty.
Now, I then search for the text that it showed me to be in the field in the full rows view.
SELECT * FROM table WHERE textfield = 'This is the text that the pop-up text-content window shows';
And it returns row 5486!
What the heck is going on here?
Quick update. If I use the SQLyog paging range buttons, and only view say 5000 rows at a time, and then start the first row at say 70k, then the empty rows show empty. But when I try to view all of the rows at once and scroll to the end, that is when the text field content is not lining up with the proper rows. It's not just the empty rows either. None of the text content rows are showing the proper text content when I click to view the content and it pops up in the text view window.
-
November 15, 2010 at 12:08 pm #31553peterlaursenParticipant
It would be easier if you provided 'less talk' and 'more exact case'.
Please
* (at least) paste the output of SHOW CREATE TABLE
* (at best) can we have a STRUCTURE+DATA dump of that table. If it (zipped) is too big for attaching here (with 70K rows I think it is), please create a ticket at http://webyog.com/support and we will find a way to transfer. Everything in ticket system is confidential of course
Also please tell the SQLyog version you are using. Some basic hardware information could be useful too – in particular the amount of RAM on the system and the graphics system (video card/chip)
-
November 15, 2010 at 12:38 pm #31554peterlaursenParticipant
Another option could be to have a screen-sharing session. To arrange this please also create a ticket.
And if you did not already please also try to reboot Windows.
-
November 15, 2010 at 11:44 pm #31555marcmMemberQuote:It would be easier if you provided 'less talk' and 'more exact case'.
^ 'nice'
[attachment=1451:schema.jpg]
[attachment=1452:tabledata1.jpg]
[attachment=1453:table_textfield_view1.jpg]
[attachment=1454:table_textfield_view2.jpg]
[attachment=1455:table_rowresult1.jpg]
SQLyog Ultimate v8.63
XP Pro 64 bit
4 gigs of ram
EVGA NVIDIA GTX 275
-
November 16, 2010 at 1:47 pm #31556vishal.prMember
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
-
November 17, 2010 at 12:21 am #31557marcmMember
Hi Vishal,
You are welcome, glad to help.
-Marc
-
November 23, 2010 at 12:24 pm #31558vishal.prMember
Hi,
We have released SQLyog 8.7 GA with this fix. Refer to http://www.webyog.com/blog/2010/11/19/sqlyog-mysql-gui-8-7-released-form-view-improved-sql-formatter-and-more/
The release notes says With a large number of rows displayed GRID could display garbage and fail to identify properly BLOB/TEXT data belonging to the row.
Please find the version history here
http://www.webyog.com/faq/content/33/7/en/sqlyog-version-history.html
Regards,
Vishal P.R
-
-
AuthorPosts
- You must be logged in to reply to this topic.