Forum Replies Created
-
AuthorPosts
-
tyrathectMemberpeterlaursen wrote on Nov 23 2007, 10:42 AM:.. the current design is most intuitive.
That is undisputed 🙂
peterlaursen wrote on Nov 23 2007, 10:42 AM:As per your proposal user would manually need to 'refresh' and I think it would be an annoyance!This is true, too, and a much greater one than waiting for the objects tab contents to update on a big remote database 😉 That is why, if ever this gets implemented, users should be able to turn auto-updating on and off, and secondly, this setting should not apply unconditionally to just any object but users should be able to make different settings based on the object type, as you already suggested in your post.
tyrathectMemberpeterlaursen wrote on Nov 22 2007, 02:13 PM:I think the comparison with Windows Explorer does not quite 'hold water'. SQLyog is a database client and will need to communicate with the server whenever something happens at the client side. In this case we send a USE statement.Well, it was just an example to illustrate my point 😉
Anyway, what I'm wondering about is that it takes the objects tab exceptionally longer to display all the tables in a big database than it takes for the tree view. Since the tab always updates it's contents automatically, this is what makes it inconvenient in this case.
However, since there are workarounds, this is not really a problem but just an usability inconvenience which could maybe be addressed in a further release, maybe with an option in preferences to automatically switching to a specific tab when opening a database, or not to auto-update the objects tab in that case.
tyrathectMemberManoj wrote on Nov 22 2007, 03:49 PM:There is an option in preferences that may be helpful. “Always select objects tab…” keep this option unchecked and make sure you are in some other tab while clicking the '+' in the object browser. Then it won't update the Objects tab.Well, this is known to me already, as I stated at the beginning of the second paragraph of my post. The problem is always to remember to switch to another tab, it's just an issue of handling and comfort 😉
November 20, 2007 at 12:43 pm in reply to: Filling Insert Row With Values From A Displayed Row #25043tyrathectMemberHmmm… not sure, I'm not too familiar with spreadsheets and Excel/Calc's capabilities there ^^;;;
I'm not sure if I'm making myself clear about the feature I'm suggesting =^^= I'm imagining something like this: in the table data tab, right-clicking a row will bring up the usual popup menu but with one or two additional options, “Copy row data to insert row” and/or “Copy cell data to insert row” or something. Then I could edit the (copied) data in the insert row and hit the “Save changes” button which will at last physically insert the new row into the table.
November 19, 2007 at 8:06 am in reply to: Filling Insert Row With Values From A Displayed Row #25041tyrathectMemberpeterlaursen wrote on Oct 2 2007, 11:31 AM:I think we have an identical or almost identical request registered here:Hm, not sure about this, I think my request is somewhat more simple: In the “Table Data” tab, data from an existing row of the same table should be able to be filled into the insert row (last row, usually empty at first), in contrast to typing it in by hand.
Btw, I just noticed there are now browse buttons in the table data tab 🙂 Thanks, I really missed this a lot before ^____^
tyrathectMemberpeterlaursen wrote on Sep 7 2006, 03:29 PM:nope it is not adressed. I also do not think we support this authentication. There is no setting for entering the PRIVATE KEY info either.I will call in assistance here! 🙂
Well, if you ever do support it, it will be a nice feature. Until then, “my” Putty workaround can be applied to achieve public/private key authentication for SSH tunnelling.
In any case, thanks for bearing with me 🙂 This kind of nice and polite assistance is quite rare, and is another reason why I decided SQLyog is the right tool for our company 🙂
tyrathectMemberpeterlaursen wrote on Sep 7 2006, 11:17 AM:I do not believe that the OS should nmake any difference. I think there was a server problem!No, there wasn't. I was connected to the server that was used as tunnel with putty at the same time, and connected to the database server with phpMyAdmin, also at the very same time. It hosts part of the live system, too, so we would have been flooded with customer's complaints if the server would have been unreachable. I think I can fairly guarantee that there was no problem with the servers.
Our local network is ok, too, nothing was changed there, anyway (I am one of two people who would can change any settings, so…)
Aside from that, SQLyog was already working on one machine (which was on day 2 of the trial period), while at the same time it was not working on the computer right next to it (which was still on day 1 of the trial period).
Anyway. I'm quite out of computers now to install SQLyog on (without annoying people in the company, that is), so there's no more testing from me. Either you believe me, or you don't.
Aside from this, SQLyog is great and I will recommend the purchase of some licenses for our company after a few more days of testing. The described bug (if it is one) doesn't bother much, it might be solved with the full version in the best case.
Besides, there's something I couldn't find in the documentation and merely found out by coincidence. The SSH tunnel server uses private/public key authentification. Actually, I was quite surprised to find out SQLyog was working with this server as tunnel at all, since there are no settings for specifying a key. On the 3rd and 4th machine I installed SQLyog on then, I finally got authentification errors. I finally found out that the computers where I could connect through the tunnel had saved Putty Sessions (with the required key file specified) on them that had the same name as the server specified in the Tunnel Server setting in SQLyog, while the computers where I could not authenticate did have Sessions for the tunnel server, but saved with a different (abbreviated) name.
If this is addressed somewhere in the documentation, I could not find it…
tyrathectMemberpeterlaursen wrote on Sep 6 2006, 07:42 AM:You are quite sure it was not an 'error 40' ?I have installed SQLyog on 3 computers (4 since today, see below). The error message is “FATAL ERROR: Network ERROR: connection timeout”, nothing else.
peterlaursen wrote on Sep 6 2006, 07:42 AM:You will have to be more specific in describing the possible error.Ok, here's again what happens. When installing the trial version and trying to connect via SSH tunnelling, I get “Connection Timeout” errors, no matter what I do. But if I try again the next day, everything works perfectly. This behavior occured on two computers with Win98 and another one with Win2k. However, as I found out today, with WinXP it works from the first day already.
peterlaursen wrote on Sep 6 2006, 07:42 AM:It is NOT a miscalculation in the verirication of the trial period, because then it would have displyed something like “Your trial period has expired …”Well, ok, I can't really know ^^; I just thought it might be, since the connection test works from the start in the community edition, and it works after a day has passed in the trial edition.
tyrathectMemberpeterlaursen wrote on Sep 5 2006, 11:19 PM:If it has expired it willl tell you so!It has not expired, I installed SQLyog on the mentioned computers in the past two days. Problem is, on the first day I installed it (1st day of trial, 30 days left), it did not work, but on the second day (2nd day of trial, 29 days left), it does.
tyrathectMemberpeterlaursen wrote on Sep 5 2006, 09:46 AM:We cannot reproduce the HTTPS problem however!Do you seriously mean that you get “FATAL ERROR: Network ERROR: connection timeout” with HTTPS too?
Well, here is more weirdness. I re-installed SQLyog today to re-check this. Now, SSH tunnelling and HTTPS tunelling works fine, and so it does on the other machine I tried it on yesterday (and it didn't work there, either). So I installed it on a third machine today (first time there), and I got the SSH/HTTPS tunnelling errors there. I'll try again on that machine tomorrow, if it does work there then, it seems to be a bug in the trial expiration calculation…
-
AuthorPosts