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

Forum Replies Created

Viewing 15 posts - 2,521 through 2,535 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27580
    peterlaursen
    Participant

    “My host does not allow to use the sync tool as i would need 2 connections. It only allows 1 remote connection”. There we have the problem I think. In several situations SQLyog will create a seperate connection for specific tasks.

    For instance the various STOP options will create a new connection and execute mysql_kill(old_connection). That is the only correct way!

    I will ask the team to check if this is the case with backup and copy!

    Was that one thing that was changed recently?

    However if you run SJA data sync from commandline only one connection would do!

    in reply to: #27578
    peterlaursen
    Participant

    I have read your ticket with great interest of course! But I had nothing new to say. So I did not reply last night!

    I have asked you if it is possible to 'copy database' to a local server and backup from the local server?

    Alternatively you may also try data sync (would require ENTERPRISE though – but you can test with the trial).

    in reply to: #27673
    peterlaursen
    Participant

    Proposals are always welcome. But this is not on the agenda in foreseeable future I am afraid.

    I think most of this logic can be done with the 'mysql proxy'. Once proxy is running with an appropriate LUA control script you can connect to the proxy with SQLyog. Did you consider this?

    about proxy http://forge.mysql.com/wiki/MySQL_Proxy

    sample scripts: http://forge.mysql.com/tools/search.php?t=…mp;k=mysqlproxy

    in reply to: #27667
    peterlaursen
    Participant

    good observation! I think we should make it fixed-width!

    in reply to: #27663
    peterlaursen
    Participant

    I think it is commonly realized the Fedora 9 has its 'weirdities' (from time to time the Fedora community does weird things — such as Fedora 6 not to forget!). But we are 'the small guys' here so likely we will have to fix it if reproducable.

    Please tell:

    — Wine version?

    — Could you try same thing with a few other Windows programs?

    I think we have a F9 running in office and can test tommorow too! But I think it should be enogh to restart/kill 'wineserver' and not the complete OS?

    in reply to: #27662
    peterlaursen
    Participant

    damn smileys!

    The smiley in above post is a b-bracket

    in reply to: #27661
    peterlaursen
    Participant

    There is no bug in MySQL!

    Try

    CREATE TABLE `timestamptable1` (

    `TextField` varchar(20) NOT NULL,

    `DateCreated` timestamp NOT NULL default '2008-10-27 00:00:00',

    `LastUpdate` timestamp NOT NULL default '0000-00-00 00:00:00'

    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;

    CREATE TABLE `timestamptable2` (

    `TextField` varchar(20) NOT NULL,

    `DateCreated` timestamp NOT NULL default '2008-10-27 00:00:00',

    `LastUpdate` timestamp NOT NULL default '0000-00-00 00:00:00'

    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;

    SHOW CREATE TABLE `timestamptable1`;

    SHOW CREATE TABLE `timestamptable2`;

    .. and for both you will see *the first TIMESTAMP NOT NULL* in every table been rewritten to TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP.

    The FAQ also told:

    “One more detail about the situation described with point 😎 above is that if a column already exists that uses the CURRENT_TIMESTAMP keyword the server will create as “NOT NULL default '0000-00-00 00:00:00'””

    we should conider making it more clear like

    “One more detail about the situation described with point 😎 above is that if a column already exists that uses the CURRENT_TIMESTAMP keyword explicitly or implicitly the server will create as “NOT NULL default '0000-00-00 00:00:00'” …”

    in reply to: #27660
    peterlaursen
    Participant

    [attachment=1020:create.jpg]

    [attachment=1021:history.jpg]

    [attachment=1022:show_create.jpg]

    Here I create a TIMESTAMP NOT NULL. You can see the CREATE TABLE dialogue and the statement that was sent to server from HISTORY.

    After creating the server has 'translated to': TIMESTAMP (NOT) NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP.

    If this does not happen exactly like this for you it could be because you are using 6.15. I am using latest internal 7.12 build (7.12 RC2 + a few fixes). But I do not think anything changed in that respect.

    However to see *exactly* what SQLyog does, you can always check in HISTORY.

    in reply to: #27659
    peterlaursen
    Participant

    Ok .. now I checked .. and your observation is correct!

    I posted this: http://bugs.mysql.com/bug.php?id=40124

    in reply to: #27658
    peterlaursen
    Participant

    OK now I got the problem!

    “I will need two timestamps for every record: A: the original date of creation (DateCreated) and B: the last update (LastUpdate).”

    You cannot do that in MySQL as CURRENT_TIMESTAMP can only be used for the definition of *one* column. So you can declare

    1)

    TIMESTAMP (NOT) NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

    or just

    TIMESTAMP (NOT) NULL ON UPDATE CURRENT_TIMESTAMP

    for B:

    or

    2)

    TIMESTAMP (NOT) NULL DEFAULT CURRENT_TIMESTAMP

    for A:

    But you cannot do both 1) and 2). Only one can be managed automatically by the server due to table definition. The other one will need to be handled by the application code! You will need to set it CURRENT_TIMESTAMP or now() from application code. Also note that a NOT NULL timestamp will be set to CURRENT_TIMESTAMP if you set it NULL.

    I think I would do this

    for A: TIMESTAMP (NOT) NULL DEFAULT CURRENT_TIMESTAMP

    for B: TIMESTAMP NOT NULL (DEFAULT 0000-00-00 00:00:00)

    (the latter default only if sql_mode permits zero-dates – if not just use a constant like 1980-01-01 00:00:00 for instance)

    A will then be handled by the server automatically, to update B set it NULL in any update statement on that table in application code.

    I am surprised by your example that the order of timestamps matters. It seems that the old behaviour form 4.0 is preserved if no columns use CURRENT_TMESTAMP. I do not think it is documented like this. And I have not had time to check it!

    in reply to: #27651
    peterlaursen
    Participant

    This is fixed now! Can you wait till end of the week (where we hope to release 7.12 FINAL) or is this urgent to you? If so we may give you a private build or 'push in' a RC3.

    in reply to: #27656
    peterlaursen
    Participant

    I think I forgot to ask the MySQL version! What is the version? Before 4.1 (3.x or 4.0)?

    The FAQ I linked to also tells:

    “With MySQL version 4.0 and before it is a little more simpler. The server will create the TIMESTAMP as defined by user – simply. But the first timestamp in the table definition will be handled by the server like described here: http://dev.mysql.com/doc/refman/4.1/en/tim…p-pre-4-1.html: “Automatic updating of the first TIMESTAMP column in a table occurs under any of the following conditions: …The column is not specified explicitly in an UPDATE statement and some other column changes value…” In other words: with those server versions the first timestamp will basically be treated like 4.1+ TIMESTAMPS defined 'NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP'. But with those versions this is not implemented in the CREATE STATEMENT for the table. The server simply 'silently' treats the first TIMESTAMP like this! Also note that with those versions a DATETIME string constant is 'yyyymmddhhmmss' only (no “-“s, no “:”s and no SPACE). Further the parameters 'default CURRENT_TIMESTAMP' and 'on update CURRENT_TIMESTAMP' does not apply to those versions. They will return a server syntax error.”

    There is no CURRENT_TIMESTAMP possible with those early versions! Only from 4.1.x. 'first timestamp in the table' on these versions is special as compared to others.

    in reply to: #27654
    peterlaursen
    Participant

    Please read: http://webyog.com/faq/content/8/159/en/how…ith-sqlyog.html

    to define a TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

    .. simply click the NOT NULL checkbox (and do nothing else) in the CREATE TABLE dialogue!

    these two

    1) TIMESTAMP NOT NULL

    2) TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

    .. are the same in MySQL from 5.0.x (with the addition that CURRENT_TIMESTAMP keyword can only be used once in a table definition) . Create (1) and the server will 'silently' translate to (2) .. provided that CURRENT_TIMESTAMP keyword has not been used earlier in table definition!

    in reply to: #27653
    peterlaursen
    Participant

    Can you detail 'form-like'?

    in reply to: #27648
    peterlaursen
    Participant

    We have lots of recent Dell systems with no PS2 option (at least 5 of those) so we could give it a try with the USB keyboard that shipped with those!

Viewing 15 posts - 2,521 through 2,535 (of 7,398 total)