Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantI think I made it clear, but obviously not clear enough!
7.02 data sync does not support MySQL servers 3.x and 4.x. With those server versions you will need to use 6.56 (for data sync only – in every other respect 7.02 will work with those older server versions as well).
We cannot achieve the speed improvements in data sync we did with 7.02 without using server functionalities that are not in 4.0 servers and we won't compromise on the speed achievements.
You can have more versions installed at the same time. Registered users can request a copy of 6.56. If so please create a support ticket.
Maybe we will find a more elegant solution (like linking the 6.56 SJA to SQLyog GUI version 7.02). But no guarantee that we will. It depends on the demand for this. After all those server versions are not supported by MySQL/Sun any more and the day is approaching where also we will need to decide not to spend time with them.
peterlaursen
Participantnope! we cannot possibly fix issues 'backwards'. We strive to fix in first release after they have been reported. That is all we can do!
peterlaursen
ParticipantAfter (15*sample interval) it should display something like this:
[attachment=968:graphpopup.jpg]
peterlaursen
ParticipantThe only explanation I can give is that there is no data yet. For how long has MONyog been collecting data for this server and what is the sample interval setting. I see 'initial time' on the right so it seems that there is still no full period to display.
peterlaursen
Participant“I have a record that won't sync from one MySQL table to another on a different server.”
Can you provide a reproducable test case for this? (preferably a small dump from both source and target – and please zip or tar into one file).
And still you may post a ticket if you want privacy!
peterlaursen
Participant7.x Data SYNC is not compatible with MySQL 4.0 and 3.x. The functions we use for achieving the speed improvements do not exist in 4.0 and 3.x. Currently you will need to use 6.56 for Data Sync if a 3.x or 4.x server is involved. You can have 6.x and 7.x installed in parallel. I hope (but cannot guarantee) that we will find a better solution soon.
You may download SJA for Linux 6.56 from here:
peterlaursen
Participant1+2) Please go detailed through the registration pages for those servers! Did you check 'linux' and 'replication' options?
3) The documentation currently available is what you see in 'help' after installing. You will not need to purchase .. documentation is the same for a trial and a licensed version.
peterlaursen
ParticipantThis has been fixed in trunk now. Fix will be included in next 7.1 beta/RC release. Estimate is Tuesday next week.
If you are in urgent need for this fix now please contact us through the ticket system.
peterlaursen
ParticipantOK .. we discussed this and realize that our presentation is not good enough (the logic is however).
So will will fix this before 7.1 FINAL release. We do not consider it an emergency, so developers will finish what they have started. I think we can start on this around Monday. I propose:
HISTORY tab: no change
MESSAGES tab: exec:
, transfer: , total: status bar:
/ . If there is room for it some text too! All times will be formatted hh:mm:ss:mss.
And of course it will still be based on TIMESTAMPS collected on client machine (because that is the only way)
As regards the request to display 'on the fly time' I do not think we can do this this time. It will require a seperate thread (similar to the thread that displays the 'red cross' STOP icon while a query is running). This is no principal difficulty however – only quite a lot of work!
There is still time for anybody to comment and propose!
peterlaursen
ParticipantYou can search the Forums here and you will find similar discussions!
When we changed last time we asked users, but had very little feedback. But I agree that it is not very intuitve. We also have a few more releated requests like
* 'in progress' time indicator
* formatting hh:mm:ss:xxx
peterlaursen
Participantpeterlaursen
ParticipantNothing really you can do .. except wait for us to implement an option to 'keep connecton alive' (execute mysql_ping() API function at short intervals). I think we should give that priority after 7.1 release. Looks like lots of wireless routers in particular have problems with reconnecting!
Can you tell your router system?
peterlaursen
ParticipantI do not think this is related. This is a plain Wine issue on that distro and with that Wine version. Wine sometimes generates lots of errors but they are not serious! Failures to generate correct sync script is not affected by such. If SQLyog can execute queries against MySQL and have results returned thers may be millions of OS-errors and warnings.
We do not require a DUMP with data. A *structure-only* DUMP will do. Without it we cannot do progres
Also: can you tell the MySQL version, and if it is 5.x+ please also tell if you make use for Stored Procedures, Triggers, etc.?
peterlaursen
Participant1) I think that can be done with CSV rather easily. Not so sure about other options (SQL in particular) – we will need to look into the code!
2) with 'Export (CSV/HTML/SQL/…) to screen only' to you figure that an Editor tab should be opened and the result inserted here? I cannot think of any other program object that can handle such data!
We will return to this request when 7.1 final is released. But please detail as much as possible – in particular this 'to screen only'!
peterlaursen
ParticipantI did not mean to frighten you away!
Please provide a test case for reproducing this! We will solve with priority then. But without further information we cannot do anything!
-
AuthorPosts