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

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: #26219
    RandyJohnson
    Member

    I have the ENTERPRISE version and yes autocomplete works part of the time.

    If the server is not going to solve the problem it would be nice if Webyog did.

    However the bigger issue to me, is that on misspelled tables/fields the server does not give me an error.

    Until you actually execute the procedure, the misspellings do not throw an error.

    In order for autocomplete to work Webyog has the knowledge of what the table name should be and its corresponding fields.

    Randy

    in reply to: #26214
    RandyJohnson
    Member

    I believe that it was 6.12

    in reply to: New Event Feature #20353
    RandyJohnson
    Member

    Is there any schedule as to when this feature will be added?

    I would agree that EVENTS would be just another folder similar to VIEWS, STORED PROCS, and FUNCTIONS.

    Randy

    in reply to: #25526
    RandyJohnson
    Member

    Peter…

    I figured out where to bump the max-packet size setting and it is working correctly.

    Thanks for all of your help.

    Randy

    in reply to: #25524
    RandyJohnson
    Member

    Peter…

    Thanks for your assistance.

    The actual error is listed below and was extracted from the error file that Webyog created.

    Error occured at:2007-12-11 17:03:02

    Line no.:682

    Error Code: 2006 – MySQL server has gone away

    The MySQL is 5.1.22 and is located on my local machine. There is no network connection per se.

    #1 Where exactly do I configure CHUNK and BULK? The server or Webyog? I suspect that you are correct in that once CHUNK and BULK are configured properly it should work with out any problem.

    #2 Since the failure is always at the same point and the same table, I copied the particular table into another database and SQL dumped it from which I am attempting the restore.

    #3 The table only has one key that is indexed on two numeric columns. The table is also an InnoDB table.

    Thanks in advance for your continued assistance.

    Randy

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