Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Selecting Blobs #30452

    I just noticed that HeidiSQL v5.0.0.3031 does this. They use SELECT LEFT(BLOBcolumn, 256). And it displays my table quite fast. Then, when i ask to view/edit/insert the BLOB for a cell, they do that separately.

    For now, HeidiSQL saved me from using the time-consuming PHPMyAdmin.

    I had trouble with HeidiSQL's export/import features, messing up one database, that's how i got to SQLyog which worked like a charm. I would love to have an option in SQLyog to solve my BLOB issue as well.

    Either way, anyone who spends day after day creating such a great tool and giving out a free version of it has my greatest appreciation.

    Many thanks!

    in reply to: Selecting Blobs #30451

    “Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.”.

    I'm using the latest version (i guess, downloaded 2-3 days ago).

    I'm not talking about the scrolling delay… i'm talking about loading a table with several row, where each row has a BLOB field with a 300 – 500 kb image. When loading the table data, it has to download 500 kb x 200 images (they're actually more then 200) , that means loading 100 MB over an internet connection before displaying the data.

    I wanted an option to download the data without actually downloading the BLOBs when i display the table contents (just the BLOB size that you already show) , and to fetch the BLOB for a cell only when i double click on that cell.

    This way it should only load 200 or more rows of text, then display the table data, and just download the BLOB for a cell only when i ask for it. Downloading BLOBs from the beginning along the text attributes makes it impossible to display more than 5 or 10 rows, the download time would be criminal.

    I tried to “trick” my MySQL database using a view in which i used a case statement that would only display LENGTH(myBLOBcolumn), but i need to update data in the table and be able to insert BLOBs as well, and that case statement makes my view impossible to edit/insert…

Viewing 2 posts - 1 through 2 (of 2 total)