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

Forum Replies Created

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • in reply to: Error Opening Sync File #35008
    CoastalGuy
    Member

    Found my problem, no response needed. Thanks. Had previously set these up on my old PC and was using the prior partition locations. Found that my sql files were listed under the D: instead of E: drive so it could not be found and was creating the error.

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32196
    CoastalGuy
    Member

    Supratik,

    Seems you did it again. Changed the InnoDB dir path in my.cnf and it seems to be working fine now. Thanks again for your great advice.

    Regards,

    Coastalguy

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32193
    CoastalGuy
    Member

    Supratik,

    Getting emails now.. thanks,

    No rush on this. Glad we finally had a problem you were able to replicate at your end.. was thinking maybe it was me? If it will help, I created another InnoDB table under XP where I tried to change the table type under Ubuntu. As with opening the table, changing the table type also errs that it cannot find the database. Apparently, no matter what you try to do with a InnoDB table created under XP, it can't find it under Ubuntu.

    I await your findings… good luck,

    Coastalguy,

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32191
    CoastalGuy
    Member

    Just an aside, I was wondering why I wasn't getting any emails (or RSS feed) on your responses? I copied the url from the RSS feed at the top right “View New Content”, but get nothing. I checked my spam site and they aren't there either. Thanks,

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32190
    CoastalGuy
    Member

    I wasn't certain how to run the EXECUTE command you provided, but I went into the Query box and entered that command. The result was: variable name: “lower_case_table_names”, Value: 1. If I did this right, I guess the value of 1 is already set? If I did it wrong, please let me know the steps for this.

    Also, on all of the databases and tables, I always use purely lower case, but sometimes with an underscore if 2 words (i.e. database = test_myisam, table = table_myisam. I'll try it using just one lowercase word for both the database and table.

    Remember that I am a total novice using your client, especially any Query or other commands. If you need any info requiring commands, please provide how I should perform the task. I know how to create databases, tables, fields etc. and enter records either directly or via PHP code. Anything else on your client, I have to research and will be guessing at the very best.

    Thanks,

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32188
    CoastalGuy
    Member

    Ok,

    Further to my response above, I had to reboot to Ubuntu to get the mount information. I am mounting the Windows partition (holding the databases used by both Ubuntu and XP), in the fstab file for mounting on boot up.

    UUID=XXXXXXXXXXXXXXXx /media ntfs defaults 0 0

    Now, under XP, I created 2 databases, one with a MylSAM table and one with a InnoDB table, entering several records into each. As thought, under Ubuntu, the MylSAM table opened fine while the InnoDB file produced a does not exist error.

    Trying it in reverse, under Ubuntu, I deleted both of these databases and re-created them as I did in XP, one with a MylSAM table and one with a InnoDB table. Back in XP, both opened fine.

    Obviously, under Ubuntu, there is a problem opening InnoDB tables created under XP, but not visa versa. Consequently, for the few InnoDB tables I might need, I can always create them under Ubuntu and have them available under both OS's. For MylSAM tables, I can create them under either OS.

    This is fine with me, “unless you want to pursue this further”. I have a solution which I am fine with so as to not have to bother you further.

    Regards,

    Coastalguy

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32187
    CoastalGuy
    Member

    Yes, as you suggested, I changed the LAMP's for both XP and Ubuntu to XAMPP, both running the same versions (instead of my Sokkit). Also, both of your SQLyog's are running the 9.0 version (just updated).

    Now the SQLyog in Ubuntu is running under the Wine application as a Windows program. Again, all of my databases created under the “very” old version of SQLyog created files of .frm, .myd and .myi (so I assume they were all defaulted to MylSAM tables)? When I use MylSAM tables (.frm, .myd & .myi files) under the 9.0 version of SQLyog, no problem. But, when creating InnoDB tables (under XP) (.frm files only) it works under XP but not Ubuntu, where I received that error that the database doesn't exist.

    I have not tried this in reverse though, creating an InnoDB table in Ubuntu, and then trying to open it under XP. If you think this might be an important factor, I will give it a try.

    Coastalguy

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32184
    CoastalGuy
    Member

    Peter,

    I only checked into the files, to see if I could see any difference on the databases where it's tables opened on SQLyog under both Ubuntu and XP, versus the new database I created under XP, but then could not open the table under the Ubuntu installed SQLyog.

    That is when I found that the table type of MylSAM created .frm, .myd and .myi files and worked under both OS's. The one I created under XP that wouldn't work under the Ubuntu installed SQLyog, was as you noted, possibly created as InnoDB table type.

    My question then, is why a table created as a InnoDB under the XP Sqlyog, will not open under the Ubuntu Sqlyog? Trying to open this table under Ubuntu results in a “Mysql Error #1146, table does not exist. My databases are fairly simple where I can use the table type MylSAM and not have this problem, but I was just curious if you had any ideas, in case I ever need to use a InnoDB table type. If not, don't worry about it.

    Regards,

    in reply to: New Sqlyog Error Reading Old Sqlyog Database #32182
    CoastalGuy
    Member

    Peter,

    I probably don't understand everything on this, but I went into SQLyog and using the menus in it, created a new database and table and entered some data. I then went to the folder where databases are stored, and under the folder for the new database, were the files db.opt and tablename.frm. When I looked in the folders for the other databases that I previously created through the old SQLyog, inside were .frm, .myd and .myi files. I haven't a clue what you mean by they can't be created through a client but only on a server, or that they couldn't be created with just db.opt and tablename.frm files, but they were the only files for the database I created using the SQLyog, 8.82, application for my local LAMP.

    But since then, I did some research, and found notations for the .myd and myi files and the table type of MylSAM. I went back into SQLyog, accessed the table and changed the type to MylSAM. Sure enough, when I looked in the folder for that database, there were .myd and .myi files. Additionally, I could then successfully open the table in the SQLyog installed on my Ubuntu OS.

    Obviously, the default must have been for MylSAM table types when I created databases under my old SQLyog as .myd and .myi files were created for all of them. Now I am not sure what table type was created by default when I created the new table that only created db.opt and tablename.frm files, and that could be opened in the XP version but not the Ubuntu version, but apparently there is still a quirk for whatever table type it was.

    Anyway, MylSAM table type is fine with me and it works for everything I need, so please forget the entire thing. I'm not sure why you are jumping on my request, apparently expecting me to be an expert and possibly quoting something in error. Anyway, in the future, I will do Google searches to hopefully find a resolution for any problem I encounter.

    in reply to: Mysql Connection #32076
    CoastalGuy
    Member

    To: Advanced User,

    The results of the command: mysql -h localhost -user root -p gave me the following:

    The program 'mysql' can be found in the following packages:

    * mysql-client-core-5.1

    * mysql-cluster-client-5.1

    Try: sudo apt-get install

    I am using XAMPP for linux: xampp-linux-1.7.4.tar.gz (the compressed file that I installed).

    When I start XAMPP, with the command: sudo /opt/lampp/lampp start – It starts Lamp, Apache, Mysql and the FTP successfully.

    As I mentioned, Apache and PHP are working, as indicated when I load my websites under localhost. Initially, I could not get the databases to open under my websites, until I copied my databases from my partition under Windows, to the XAMPP folder for databases – /opt/lampp/var/mysql. Once I did this, my databases loaded and displayed fine.

    I did change the Apache DocumentRoot and to my exising Windows partition with my websites which worked as localhost (once I added the partition to mount under fstab). Have not been able to get my mysql databases to work though, unless I copied them to the XAMPP database folder (even though they are a sub-folder of localhost). However, I did try the my websites under the XAMPP localhost directory, by copying my websites to /var/www with the DocumentRoot and to the this default XAMPP localhost location, but with the same results with the databases.

    localhost = /media/Sokkit (my existing Windows folder)

    mysql databases = /opt/lampp/var/mysql (XAMPP default database folder)

    Thanks for your help,

    Regards,

    Coastalguy

    in reply to: Mysql Connection #32075
    CoastalGuy
    Member

    Peter,

    I'm sorry. Having upgraded to 8.8.2 Community, from my old 4.05 version, (as you requested) on my Ubuntu Meerkat “Wine”, it is still giving me the 2003 error.

    I just wanted to let you know that I also upgraded my 4.05 to the 8.8.2 Community on my Windows XP and that worked fine.

    in reply to: Mysql Connection #32072
    CoastalGuy
    Member

    Further to my last response above, under Windows XP, I uninstalled the 4.05 version and installed the 8.8.2 Community. When I set up my first database connection, Using localhost, I also received the 2003 error as I did in Ubuntu. But I forgot to start my LAMP under Windows. Once I did that, it connected fine. It almost seems as if MySQL isn't started on the Ubuntu LAMP, however as the php opening my databases, on my websites, work fine using localhost as the host, and with my phpmyadmin working also, that doesn't seem to be the case, unless there is something unique going on with it..??

    in reply to: Mysql Connection #32071
    CoastalGuy
    Member

    Downloaded and installed (in Ubuntu Wine), 8.8.2 Community. localhost now gives me a 2003 error instead of a 2005? Again, localhost works fine for my website databases running under Apache & php and also for phpmyadmin (http://localhost/phpmyadmin). The LAMP I am using in Ubuntu is XAMPP and not those available under synaptic software package. As my websites, PHP and PHPmyadmin is working with localhost, not sure this would be the problem?

    Note that the only reason I am using the community version, is that the price of your main version is very high. I would be agreeable to $40 or so, but your price is just beyond my budget.

    Thanks again,

    in reply to: Mysql Connection #32069
    CoastalGuy
    Member

    Ubuntu 10.10

    Wine 1.3.16

    SQLyog 4.05 (This is the version I have been using on XP for years. Has been all I need so haven't upgraded)

    I am using Dual Boot to a separate install of Ubuntu (Not within Windows).

    SQLyog is installed on Ubuntu with Wine.

    i) telnet localhost 3306:

    …..trying ::1…

    …..trying 127.0.0.1 (telnet unable to connect to remote host: Connection refused

    ii) Not sure how to do this.. Can you give me the steps? (Fairly new with Ubuntu but learning).

    iii) Used 127.0.0.1 instead of localhost and received 2003 error (not the 2005 error with localhost).

    Thanks,

Viewing 14 posts - 1 through 14 (of 14 total)