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

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Error No. 2006 Mysql Server Has Gone Away #21381
    Yuri
    Member

    Really annoying,

    Since the 5.11 version my connection is lost for about every 2 minutes or such. It happens over my intranet and over the internet with several mysql versions.

    I'm going back to the previous version untill this bug is solved.

    b.t.w. i usually connect to LARGE databases, “rebuilding tag files” takes a LONG time, is it really neccecary to do this every time i connect?.

    Does this have anything to do with the “gone away” bug?

    in reply to: blob field slow, ferefence cannot be read #15969
    Yuri
    Member

    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).

    in reply to: blob field slow, ferefence cannot be read #15966
    Yuri
    Member

    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…

    in reply to: SQLyog Max upgrade price #15524
    Yuri
    Member

    praying…

    in reply to: Fulltext index not displayed/blob columns too long #15508
    Yuri
    Member

    And what about the full-text index not showing up ?

    in reply to: Fulltext index not displayed/blob columns too long #15506
    Yuri
    Member

    Sorry, the issues about the column names are already solved

    in this thread

    the bug not showing the fulltext-index remains (or did i miss a checkbox elsewhere in the program)

    in reply to: I'm missing three things in SQLYog #14340
    Yuri
    Member

    No offence taken.

    Agreed, SQLyog ís an excellent tool; that's why i bother to start this discussion.

    1__________

    True, but when my application is in development-mode: after a few days of testing e.t.c. the tables are full of dummy-text and the auto-increment's rise up to 200. My database has about 34 tables right now and just to keep the things bright & clear i sometimes like to 'reset' all tables (removing the data and resetting the auto-increment). Dropping and re-adding the column works fine, but it is a little time-expensive on 34 tables. On the other side (like you said). A “reset” button on a table makes it way to easy to be clicked without concidering the concequenses. (but i would really prefer it though..)

    Why i want to reset the auto-increment… ehh.. It's just like cleaning up your room after you made a mess of it. Just get things `clear` when you start to develop the next part of your application. And when the application is up & running you really don't want the auto-increment starting at `ID` 3000 or so.

    2___________

    I'm not talking about copying data from table 2 table, but about copying data inside the same table for testing-purposes. Just to see how your user-end application looks like if there are 800 records in your table.

    3___________

    Thanx for the tip.

    Greets,

    Yuri.

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