Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantWe do not support scheduled export to CSV. Only export to SQL. If somebody told otherwise it is a mistake!
I am able to find a support ticket (#3301) where you (or at least a person naming himself 'Raul') asked for purchasing details for SQLyog. I replied to that ticket myself.
Besides asking for prices and other purchasing details you/Raul *only* told this “I want to schedule automatic export job for tables?” – no mentioning of a specific format like CSV. If you have some mail communication with somebody here, I am not locate it.
You may however use Notifications Service and execute (and schedule) a SELECT .. INTO OUTFILE … statement. But this will store the OUTFILE on the server machine. With SELECT .. INTO OUTFILE .. you cannot save to the client machine directly (as MySQL does not support LOCAL option for SELECT .. INTO OUTFILE).
I can only regret if there was a misunderstanding. However often there are 'smarter' options than CSV (what is most often quite laborious in use). Can you describe why you need this specific format? Or would you require help to put together an appropriate SELECT .. INTO OUTFILE … statement?
peterlaursen
ParticipantTo automatically insert information from mail(s) to a database, you would typically use a server-side script (Perl, Python etc.) that parses the mails and schedule the execution of such script. SQLyog cannot access the file system or the mailbox on the server. It is a client program for the MySQL server (only). Also MySQL itself has no option to access such data. You need a script/application with privleges to the file system/mail box as well as an ability to connect to MySQL.
Another option is to use SQLyog/SJA notifications service to execute an INSERT statement. But you will still need some 3rd party script/ application to prepare the jobfile.
peterlaursen
ParticipantHow much time it takes depends on how much work needs to be done!
If only a few rows differ SJA will quickly (iteratively) find the rows where action is needed and do what necessary. But if – say – 30-40% rows need action it will take some time of course!
So best practice – in my opinion – is to sync as frequently as required to keep each individual run down at acceptable time.
peterlaursen
ParticipantWe can reproduce this in XP (not in Vista).
I also understand you tell that 6.5x and 7.0 has no diffference here for you?
I am not sure really if this was introduced latedly or it always was like that.
We do not find it 'acceptable' but do not consider it a 'showstopper' either.
If the fix is not trivial we will not let it delay 7.0 final release, but will try to fix shortly after.
peterlaursen
ParticipantWe *do not* allow numbers not between 10 and 600 in the dropdown!
We cannot prevent a XMLfile to be edited from outside SQLyog. As long as it is possible to display it *somewhat reasonable* I do not think we should reject it. For me the displays 100% if zoom level is too large. That is a reasonable solution I think.
The height and width of windows probabply should be truncated a similar way (say width could truncate to 400 or so). But height can be very large (there maybe be thousands of columns in a table)
peterlaursen
Participant@Adarsh ..
you were with Webyog so long that you (should) know that statements (also DDL statements) executed from the editor are simply sent to the server, are not parsed and have no immediate effect on the GUI. They have effect on the server of course – provided that that the statement is valid. You have to REFRESH the relevant Object Browser node (in this case the connection node) to make the change visible in the GUI. Or just drop from the Object Browser context menu instead!
This applies not only to 'drop database' statement but *any* create/drop/alter statement. Just like you will have to REFRESH the DATA GRID so see the effect of DML statements (insert, delete, update) in the GUI
I do not exclude the possibility that some 'parsing layer' will be added at some later point to add 'synenergy' between GUI functionalities and Command Line/Editor functionalities (basically the alias support is some kind of parsing added recently). But it is not priority.
peterlaursen
ParticipantThanks for your feedback.
With recent program versions (you may check changelogs to find exactly when) “Set FOREIGN_KEY_CHECKS=0” is default for exports and data sync – because sometimes users 'did not think about it' — so we changed that!
peterlaursen
ParticipantIf you do not find it in usr/local/MOnyog (if using the RPM build) then nothing has been logged yet!
If you use the .gz build look in the folder tree wheere you unpacked it
Try creating a log entry by entering a wrong password in the MONyog connection screen. that will log the error. Now you should be able to search the file!
One detail: on my Linux system (OpenSuse 11) name is “MONyog.log”, not “MONyog.Log”
peterlaursen
ParticipantVerified as described. A small clarification though
1) to reproduce this open *in the same tab*. In a new tab it will paint OK.
2) it also will paint when zoom setting is changed.
peterlaursen
ParticipantPlease first try downloading once more!
peterlaursen
Participantmore correct:
“SHOW WARNINGS;” shows warning that resulted from the last executed statement *that affected a table*. Queries that do not affect tables does not reset the warning buffer!
peterlaursen
ParticipantThis looks related: http://discussions.virtualdr.com/showthread.php?t=60351
right click the drive, properties, sharing tab, Caching, uncheck “Allow caching for this folder” ..
peterlaursen
Participantwell ..
Actually every program does the same for us. Also Notepad for instance. Could you try?
Also using the ip of the remote machine and not hostname/computer name makes no difference to us.
I think Windows expects you unmount the share before detaching the remote computer! If we do this the error always pops up immediate!
(I am not sure if Windows has some 'network broadcast system' that will unmount the share automatically after some time).
details may depend on
* OS (for us Vista is faster than XP), but details may depend on OS hotfixes and servicepacks installed
* Also maybe firmware (in network cards, routers etc.) matters.
peterlaursen
Participant“This is an easy thing to reproduce – just get an sql file from another machine using a networked path, then close the application and take the other machine offline”
I still do not understand! Are you telling that then *next time* it will last very long? Please try *pin it out* how you can reproduce.
Also I think we need inforamtion about the OS. Is it Vista? I have noticed htat Windows Explorer on Vista is some respects behaves differently than XP (it seems to 'memorize) and the API calls we send from SQLyog will basically use the 'built in' file system routines.
Sorry if I am somewhat slow here …
peterlaursen
Participantone more idea: could you please try to turn off autocomplete from program 'preferences'?
-
AuthorPosts