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

Forum Replies Created

Viewing 15 posts - 3,271 through 3,285 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25895
    peterlaursen
    Participant

    I am afraid I do not understand “can I get the SJA to trigger after a mysql-update”!

    Do you want the program to start with some specified jobfile?

    What are you referring to as 'a mysql-update'?

    Please describe a little more in detail!

    Anyway also read: http://webyog.com/faq/content/27/35/en/can…-same-time.html

    SJA is a command line program that can be exectued from a batch job or from any application capable of launching external programs.

    in reply to: #25838
    peterlaursen
    Participant

    Issues added to http://code.google.com/p/sqlyog/issues/list?start=100 (check #535-536)

    The 'manage index' issue is a silly thing that we will fix in the 6.2 trunk. The other has not been decided yet!

    in reply to: #25854
    peterlaursen
    Participant

    Now and here I will only comment on this:

    “it is as if the sync job was able to cope correctly with records inserted after the start”

    Probably! When it displays the no. of rows it executes SELECT COUNT(*) after that the sync starts: it will calculate checksums on 'blocks' of rows. Next it will sync what differences are found in taht 'block' and proceed to the next block. In the meantime new rows may be added at the end. They will be found when the job reaches so far.

    By executing the sync job at shorter intervals there will be less rows that differ and the calculation and the sync will be much faster.

    Could you try creating a 'static copy' the table and sync that one?

    in reply to: #25891
    peterlaursen
    Participant

    How did you change the log file setting?

    From command line or from inside the wizard?

    Please provide a screenshot of the command line window or the relevant wizard page.

    And – as always – please tell the version number?

    in reply to: #25888
    peterlaursen
    Participant

    Now .. what would you propose we could do then?

    It is very difficult for us to use an unkwown post … 🙁

    in reply to: #25852
    peterlaursen
    Participant

    agreed, this look a little strange.

    Sync started at Mon Feb 4 16:19:36 2008

    Table SrcRows TgtRows Inserted Updated Deleted

    ========================= ======= ======= ======== ======= =======

    `dspam_preferences` 3 3 0 0 0

    `dspam_signature_data` 48807 48740 69 0 0

    `dspam_stats` 267 267 0 22 0

    `dspam_token_data` 4787426 4783407 0 0 0

    `dspam_virtual_uids` 267 267 0 0 0

    Total time taken – 1250 sec(s)

    Could you provide a test case? Without an idea of what data those 'tokens' are it is hard to guess?

    How long does the sync job run? Is it possible to block connections for other users/clients doing inserts/updates when testing? I think that actually the sync is OK when it is 'planned' but 'out of date' when finished (due to inserts on thein job-time). But the reporting is confusing then!

    Also the sja.log may provide a little more information. Please check!

    in reply to: #25775
    peterlaursen
    Participant

    Actually we do handle 'interactive timeout'.

    The problem is there are some queries which we are not passing through the reconnect wrapper! (You will find 2 different connection modules in the code) One query that does not always is 'show create table' in certain contexts.

    The 'non-reconnecting' connection module is shared with the SJA. And it seems t o be used somewhere where it should not. Please give a little more time!

    in reply to: #25837
    peterlaursen
    Participant

    1) Most of that stuff will require access to the file system. We do not have this when connecting with the C-API from a remote host. I also think that some of it will work with MyISAM tables only.

    Also what phpMyAdmin does and looks depends on the version and configuration.

    2) True. We should use the help tables of the MySQL database itself. This QB does very well in my opinion! It is a matter of time and priority.

    3) We will need to move the 'apply' button to the 'first' dialogue screen. All additions, changes and deletes could then be queued and performed in one ALTER statement. Nice proposal. I think we never observed that ourselves!

    in reply to: #25836
    peterlaursen
    Participant

    We know about those and similar issues. especially the 'clcicking in the bar itself' issue.

    We are not 100% in control becuase of the Scintilla library that we use.

    Anyway we did plan to 'work over' grid and scrollbar issues in 6.2 tree.

    Also Scintilla has been updated. Maybe better in this respect!

    in reply to: #25851
    peterlaursen
    Participant

    And then I will move your psst to the SQLyog category!

    in reply to: #25850
    peterlaursen
    Participant

    We will study this. We do plan to 'work over' the grid in 6.2 tre.

    Could you provide an example dump to reproduce with?

    Is it DATA or RESULT TAB or both?

    in reply to: #25832
    peterlaursen
    Participant

    The link to googlecode was not the best one.

    As 'usability enhancements' to the GRID we allready have those request.

    * select all/unselect all

    * SHIFT-click modifiers

    * select/unselect from keyboard (SPACEBAR has been proposed)

    But this request is not so much about SELECTING but about highlighting somehow the ACTIVE row (where the cursor is positioned).

    in reply to: #25831
    peterlaursen
    Participant

    I recognize that problem actually!

    I think that we should consider this in this context:

    http://code.google.com/p/sqlyog/issues/det…amp;q=modifiers

    Background coloring could be a light grey only (if colors are a problem) or the active row could be 'framed' with a thicker line.

    in reply to: #25772
    peterlaursen
    Participant

    I reproduced this (SQLyopg 6.16 RC and MySQL 5.0.51a)

    “To reproduce, execute as root in the MySQL server:

    SET GLOBAL wait_timeout=5

    (my addition: connect with a new conenction to establish that changed server varaibale for the conenction)

    – then add a line in a table. Wait 10 seconds, modify a value then click anywhere else or use tab/up/down to auto-save the changed value.

    – The “mysql has gone away” error pops up.”

    But I think we are talking about two different types of 'connection getting lost'!

    1)

    What you are talking about is the situation where the server *deliberately* terminates a connection because of this setting. My guess is that we do not 'get' or 'discover' any signal that connection is lost. I also think you are right about the coding details for this situation!

    2)

    What reconnect we do is that if connection gets lost due to *some accidential error on the line* we will connect by creating a new server process/thread. That you can verify by connecting to a remoter server, disconnect the network cable (or turning off the access point , stop the webserver (with HTTP tunnellling) etc. etc) , execute something (you will get some error of course – which one depends), reconnect the cable, execute again and you will get results. This is in particular usefull with tunnelling. It is very common for instance with HTTP tunnelling that the webserver interrupts the connection. Also with SSH the connection may be lsot between PLINK and SSHD or between SSHD and MySQL (but this situation with SSH we will handle in 6.2). But it is not only useful with tunnelling – with internet lines of poor quality (lots of them are!) and cheap hosting *some accidential error on the line* happens frequently. I also think that your solution will not solve this!

    We have not had focus on the 'wait_timeout setting' .. but on all types of connection errors!

    @Fuzzy .. you (and everyone) are welcome to comment on that. But I write this mostly for our development team!

    in reply to: #25770
    peterlaursen
    Participant

    If you have some specific problem that requires an earlier version, we probably can arrange that.

    However 3.x, 4.x version and early 5.x versions we cannot!

    Please create a ticket then!

Viewing 15 posts - 3,271 through 3,285 (of 7,398 total)