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

Forum Replies Created

Viewing 15 posts - 3,421 through 3,435 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25499
    peterlaursen
    Participant

    I had it confirmed that this was fixed in the trunk shortly after the 1.1 release (October 29th to be exact).

    in reply to: #25501
    peterlaursen
    Participant

    You can use ALTER TABLE ….

    In the SQLyog ALTER TABLE GUI all you need to do is to uncheck the 'NOT NULL' option and it will change from

    “`ts` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP”

    to

    “`ts` timestamp NULL default CURRENT_TIMESTAMP”

    If you want more detailed control you can copy the ALTER statement from the HISTORY tab. In the example above it reads like

    Code:
    alter table `test`.`tstest` change `ts` `ts` timestamp DEFAULT CURRENT_TIMESTAMP NULL

    change the statement to

    Code:
    alter table `test`.`tstest` change `ts` `ts` timestamp NULL

    execute and see in OBJECTS tab it has become “`ts` timestamp NULL default NULL”

    MySQL docs: http://dev.mysql.com/doc/refman/5.0/en/timestamp.html

    in reply to: #25498
    peterlaursen
    Participant

    I think that may be solved in the latest RC2 release.

    It seems to work fine for me here. Please see attached image!

    [attachment=796:Freddie.gif]

    in reply to: #25496
    peterlaursen
    Participant

    no!

    Why do you want this? Because you do not quite 'trust' the program? Or do you want to use it as a 'Query Builder' for generating ALTER TABLE queries that you want to use from other applications or scripts? Or somethng else?

    in reply to: 6.07 Broke The Http Tunnel Feature #24950
    peterlaursen
    Participant

    thanks!

    we can of course easily list the variables and sort those after length.

    in reply to: 6.07 Broke The Http Tunnel Feature #24948
    peterlaursen
    Participant

    Maybe variables like '$___mysqli_obj', '$___mysqli_tmp' were the problem?

    If you can help to get details about this, we would appreciate!

    But also your ISP may have done some silly (configuration) mistake and prefer to blame such variable names instead of just admitting that?

    in reply to: 6.07 Broke The Http Tunnel Feature #24947
    peterlaursen
    Participant

    Or was it the security module and not the tunneller that was 'tweaked' ?

    in reply to: 6.07 Broke The Http Tunnel Feature #24946
    peterlaursen
    Participant

    “ridiculously long variable names”

    Could you please download the ('tweaked') tunneller, zip and attach here and we will find out what they were!

    in reply to: 6.07 Broke The Http Tunnel Feature #24944
    peterlaursen
    Participant

    Did you try the special build that does not use 'urlencode' linked to above?

    (note that you will need to use the tunneller shipped with that!)

    in reply to: #25495
    peterlaursen
    Participant

    If there is a way to specify the dial-up with a commandline then the dial-up can be first step of a batch job. I also think that most dialers can be configured to close the connection after a specified period of inactivity.

    in reply to: Insert Html Weblink #25265
    peterlaursen
    Participant

    to create a link like this the HTML is like

    Code:

    Every browser has an option to display the source of a webiste. It is normally in the 'edit' menu. Try this with the page that you refer to here (and search for 'Download')!

    in reply to: #25493
    peterlaursen
    Participant

    “the central machine will establish the connection” … when you connect to a MySQL server it is not a 'machine' that establishes the connection but a 'mysql client' program.

    I suggest you try to install SJA (windows or linux version) on the 'central machine'.

    You can create various type for SJA jobs like

    * a sync job for tranfer of data

    * a notifications job for deletion of data after transfer

    .. and you can build batch jobs with more SJAjobs, schedule with whatever scheduling facility is available etc.

    Please start reading http://webyog.com/faq/content/27/114/en/in…agent_-sja.html

    in reply to: #25492
    peterlaursen
    Participant

    You should upgrade to SQLyog 6.x!

    SQLyog 5.x uses ANSI internally. For that reason special characters that do not belong to the ANSI codepage of the client machine LOCALE cannot be displayed. For instance central european (Czech, Polish etc) special characters cannot be displayed in a machine running a western locale.

    But I think in your situation you should select 'utf8' as the charset for the connection in the connections manager (if server default is not utf8). Then all western languages (ANSI western codepage) will display correctly. You can execute

    USE mydatabase;

    SHOW VARIABLES LIKE '%character%';

    .. to get all relevant server charset information. But I am 99% sure that in you situation you have 'latin1' as server default and data in utf8. So if you have 'default' selected in connection manager you will get this. You may also change the server default in the server configuration file (if you have access to it).

    SQLyog 6.x uses UTF8 internally and handles all character sets supported by MySQL. Everything is fully automatically here. You will not have to do anything particular – and not specify a charset for the connection either! Refer to: http://webyog.com/faq/content/34/148/en/do…y-language.html

    in reply to: #25475
    peterlaursen
    Participant

    Please provide a test case (table dump + a query) where it is reproducable for you!

    in reply to: #25482
    peterlaursen
    Participant

    Just in case I did not make things clear enough:

    We will help you out if you create that ticket!

Viewing 15 posts - 3,421 through 3,435 (of 7,398 total)