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

Forum Replies Created

Viewing 15 posts - 196 through 210 (of 258 total)
  • Author
    Posts
  • in reply to: Manage Relationships #13946
    CalEvans
    Member

    Yes, I've used it extensivly to build relationships. The most common problem I run across is forgetting to build the index first.

    Exactly what problem are you having?

    =C=

    in reply to: Connecting using port 80? #13941
    CalEvans
    Member

    It is possible to connect on a different port, I used to connect on 3300. I was using SSH to tunnle 3306 form one server to 3300 on my desktop. However, I've not tried to use any type of proxy server between my client and the server.

    Can you give more detail? Are you connecting to a server running on 80?

    Are you trying to run over 80 to get through a firewall?

    =C=

    in reply to: GPL #13851
    CalEvans
    Member

    The following should be considered an opinion, not a statement of fact. (ok, it's a statement of fact from my POV. 🙂

    Joe,

    I'm not sure I can remove your fears. But I would like to ask. Do you use Windows? Why if it's not Open Source?

    SQLyog is a great product. Open Sourcing it would not necessarily make it a better product. It would make it a more open product.

    I love Open Source and am an evangelist of it where ever I can be. However, I will not refuse to use a product based solely on the concept that it is not OS. You use Windows, but it is not open source. Why hold SQLyog to a different standard simply because you did not have to pay for it?

    It is not true that user supplied patches insure stability. When a project is properly managed, open source or not, it will be stable. User supplied patches are just as likely to induce instability as closed source patches.

    Soren, when you abandoned mysql-front, was it because it did not work and the developers left or just because the developers left? I can name at least 1 program that I use that hasn't been in development for 3 years. However,it still works, works well and I see no reason to look for another one.

    The simple answer to what I would do if it went away is what I always do in that situation. Find something else. BUT, knowing what I know of the development team, and having tested the product for several months I can say with confidence that if they were to stop working on it tomorrow and close up shop, I could use the product for the next 1-2 years without a problem.

    (IMHO) phpMySQlAdmin is a PITA. Give me SQLyog any day. I'd rather use the CLI than try and wade through endless screens to get things done. But that's just me.(/IMHO)

    I respect any author's right to choose how to license his/her software as I expect people to respect my right to do the same. When I release GPL code it is because I want to, not because I feel the need to. And when I decide to keep my product close source, for whatever reason, it is for the same reason. If you decide, for your own reasons, not to deploy this product; I respect that decision as well. 🙂

    Please don't take any of this as argumentative. I'm really just trying to state my position.

    HTH,

    =C=

    in reply to: Connection problem error 1130 #13928
    CalEvans
    Member
    Quote:
    the % does not seem to work on my FreeBSD server ver of mysql in the command.

    GRANT ALL ON *.* TO root@% IDENTIFIED BY “password”;

    Sorry I missed the conversation. Glad you got it working. I have found on the Linux version of MySQL that I usually have to use:

    Code:
    GRANT ALL ON *.* TO 'root'@'%' IDENTIFIED BY “password”;

    Note the quotes around the login name and the % .

    I'm not sure why but sometimes it works without it and sometimes it does not. however, it always works for me with the quotes.

    =C=

    in reply to: Spaces in the column names are not supported #13933
    CalEvans
    Member

    I think this is more of a mysql issue than a SQLyog issue. mysql supports spaces in the column names but the names must be surrounded by back-ticks. (`). I know this is true in all other cases but I don't import from ODBC or flat files much so I don't have anything to test with.

    create a test file with back-ticks around the file names and try to import it. See if that doesn't solve the problem. (Let us know here either way.)

    =C=

    p..s (IMHO)Spaces in field names and table names are bad. Mkayyyyyy.(/IMHO) 😀

    in reply to: Connection problem error 1130 #13923
    CalEvans
    Member

    This is a mysql error. You are not allowed to connect to this server from your client. Adjust your user permissions and try again.

    =C=

    in reply to: CR/LF in text files #13921
    CalEvans
    Member

    I understand your problem as I've run into it many times before. However, I disagree as to the solution. I like the fact that SQLyog is not 'feature rich' as some others. It is a tool with the minimum features necessary to do the job. This is an issue that can easily be dealt with in a number of ways. I don't think it is SQLyog's place to fix the problem.

    That having been said, have you tried specifying n AND the code for CR ? (Don't know it off the top of my head, sorry.) If SQLyog will not allow you to specify more than 1 code in the line termination box then THIS is an issue they should deal with.

    =C=

    in reply to: Horizontal scroll bar is hidden behind status bar #13910
    CalEvans
    Member

    Confirmed. And in the version I'm running, resizing no-longer brings the scroll bar back to it's full size.

    =C=

    in reply to: Copy Table/Data – Drops Auto Increment #13908
    CalEvans
    Member

    Let me restate the problem to make sure I understand it. (Good chance I don't!) 🙂

    You copied a table structure over to a new table.

    The original table had an autoincrement field and the next value was not 0.

    The new table had an autoincrement field but the next value was 0.

    If this is correct then the problem is a misunderstanding. What SQLyog does when you copy a table structure only is it creates the new CREATE TABLE DDL and then executes it, just as if you had done it by hand only giving the table a new name. Thus the autoincrement value *SHOULD* be 0. (NOTE: This wouldn't happen if you copied the data also simply because it would have issued the appropriate number of INSERT's.)

    So, the program is actually doing what it's supposed to do. A question for the developers is do you feel it is appropriate to add an option into the COPY TABLE that would automatically set the next autoincrement value? (There is a command for it but I forget it at the moment.)

    IMHO, no. But that's just me.

    HTH,

    =C=

    in reply to: Error No. 2003 #13827
    CalEvans
    Member

    Going by the image you posted (on the web) you are trying to connect to localhost. While it is true that you can assign any IP address you want to localhost it is almost universally accepted that localhost = 127.0.0.1. It looks to me like you are trying to connect to a mysql server running on your own local machine.

    Some tips for debugging:

    🙂 Make sure that you really WANT to connect to a server running on your machine. (It's possible but it's not the common case)

    🙂 Make sure that you have a database INSTALLED on your local machine.

    🙂 Make sure that the database installed on your local machine is up and running.

    🙂 Make sure the database installed and running on your local machine is accepting connections on 127.0.0.1 (Poke around in my.cnf it's the bind-address directive. If it's there, make sure 127.0.0.1 or localhost is listed as one of the addresses.)

    🙂 Make sure the database installed and running on your local machine is listening to port 3306.

    An easy way to verify most of this is to try to connect and then check your log file. if you get something in the log file then the server is up, running and installed. The error message you get should help you find the problem. If you don't get anything in your error log then either the server is not running, not accepting connections on 127.0.0.1 or not listening on 3306.

    For the record, this isn't really a SQLyog problem. (Not criticizing, just setting the record straight.)

    HTH,

    =C=

    in reply to: Suggestion: auto-select database #13862
    CalEvans
    Member

    I second this request and call for a vote. 🙂

    =C=

    in reply to: Scheduled execution #13893
    CalEvans
    Member

    no

    =C=

    in reply to: synchronising data #13879
    CalEvans
    Member

    Curious, do you move data (large quantities) from your development to your production? My usual way of synchronizing the two is o use mysqldump -opt on my production and sucking it into my development. I rarely move data the other way except for domain table entries.

    =C=

    in reply to: semi-colons #13885
    CalEvans
    Member

    I'm unclear as to what your problem is. Is it that your data has semi-colons in it? If so, simply remove them. (By hand if you don't know how to write the appropriate SQL code) They are not required for either SQLyog or mysql to work.

    Where did they come from? I don't use the blob editor often but when I do I never get errant characters of any kind inserted into my system.

    =C=

    in reply to: Tab Completion? #13804
    CalEvans
    Member

    Wonderful!

    And if it actually connected to mySQL databases and allowed you to manipulate data and scructures, you post might be relevant.

    =C=

Viewing 15 posts - 196 through 210 (of 258 total)