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

Forum Replies Created

Viewing 15 posts - 241 through 255 (of 258 total)
  • Author
    Posts
  • in reply to: Alter Table Difficulty #13720
    CalEvans
    Member

    What OS is the server running on? This really sounds like a permissions issue of some kind. (At least that's where I would start looking.) I've never seen these errors.

    Can you issue the statemetns in the mysql client directly?

    Debuging 101: Start Eliminating until the problem is gone.

    =C=

    in reply to: error #13717
    CalEvans
    Member

    QUOTE
    HI, I've installed MySQL and php. Everything seems to work but I get a 403[Forbidden] error.

    I did the report and this is it.

    This Report was made using the WinMySQLAdmin 1.4 Tool

    This is permissions problem. 403 means that IIS does not have permission to read the directory the page is in.

    Since you are on Win2k, browse to your document root, right click on the folder and make sure that whatever user IIS is running as has permission to read that dir.

    HTH,

    =C=

    in reply to: Error 1064 #13699
    CalEvans
    Member

    Obligatory link to the docs.

    Those are not quotes, they are backticks. MySQL allows them around table and field names work around the restriction of reserved words and special chrs. While I don't personally use them in my coding, they are a safety measure in SQLyog to make sure that it does not try and execute queries with reserved words in them. (try show table status from `mysql`; in a mysql client.. It should work.)

    The ; is required and being used but it is not being echoed in the history file. Not sure why but this is not a bug. SQLyog IS putting them in where it counts, in the actual command stream. Check the log file from your mysql server. They should be there. (Mine always are)

    I agree that there is a problem somewhere but these are it.

    What version of mysql are you using?

    Obligatory link to the docs.

    The current syntax of SHOW TABLE STATUS is new in version 3.23. The previous version (SHOW STATUS `mysql`;) does work with my version of 3.23.54a. I'm not sure when it stopped working but you could be right in the fact that it's a version think.

    HTH,

    =C=

    in reply to: Startup Time #13702
    CalEvans
    Member

    Have you tried turning off just certain options in McAfee instead of shutting it all down? I'm guessing it's got something that is either monitoring all disk activity or all network activity that is choking it down. (Just a guess)

    =C=

    in reply to: Semicolon before SQL? #13673
    CalEvans
    Member

    3+ months of testing this tool and I never noticed that. 🙂

    The ; before the statement is so you don't get an error if you haven't put one at the end of the last statement. It probably needs to stay. But I agree that it would be nice to stick the closing ; on there for us.

    =C=

    in reply to: Table Diagnostic #13666
    CalEvans
    Member

    Dunno.

    The 4.0.10 manual does not list any changes to check table. type=extended is still listed as a valid command.

    2 more things to check.

    Can you paste the check statement into the mysql command line tool on the server? Does it work?

    Can you cehck 1 or 2 tables instead of all of them? Does it work?

    =C=

    in reply to: Table Diagnostic #13664
    CalEvans
    Member

    What's your tabletype?

    in reply to: Table Diagnostic #13662
    CalEvans
    Member

    Did the History window show the actual query being issued? If so, please post it so we can see it.

    =C=

    in reply to: Foreign keys #13649
    CalEvans
    Member
    Code:
    create table `test`.`Cars` (
    `ID` bigint   NOT NULL ,
    `name` char (20)   NOT NULL  ,
    PRIMARY KEY ( `ID` )
    )type=InnoDB row_format=dynamic;

    create table `test`.`Owners` (
    `ID` bigint   NOT NULL ,
    `name` char (15)   NOT NULL ,
    `IDcar` bigint   NULL  ,
    PRIMARY KEY ( `ID` )
    )type=InnoDB row_format=dynamic;

    alter table `test`.`Owners` add index `indexIDcar` ( IDcar );
    alter table `test`.`Owners` add foreign key (IDcar) references `Cars` (ID) on delete restrict;

    Ok, I finally broke down and executed the code above (cut form your first post and pasted into the command window of SQLyog.

    I get:

    Code:
    CREATE TABLE `Cars` (                                                                                                                                        
            `ID` bigint(20) NOT NULL default '0',                                                                                                                        
            `name` varchar(20) NOT NULL default '',                                                                                                                      
            PRIMARY KEY  (`ID`)                                                                                                                                          
            TYPE=InnoDB ROW_FORMAT=DYNAMIC                                                                                                                              

    and

    Code:
    CREATE TABLE `Owners` (                                                                                                                                                                                                                                                                
            `ID` bigint(20) NOT NULL default '0',                                                                                                                                                                                                                                                  
            `name` varchar(15) NOT NULL default '',                                                                                                                                                                                                                                                
            `IDcar` bigint(20) default NULL,                                                                                                                                                                                                                                                      
            PRIMARY KEY  (`ID`),                                                                                                                                                                                                                                                                  
            KEY `indexIDcar` (`IDcar`),                                                                                                                                                                                                                                                            
            FOREIGN KEY (`IDcar`) REFERENCES `test.Cars` (`ID`)                                                                                                                                                                                                                                    
            TYPE=InnoDB ROW_FORMAT=DYNAMIC

    create table `test`.`Owners` (
    `ID` bigint   NOT NULL ,
    `name` char (15)   NOT NULL ,
    `IDcar` bigint   NULL  ,
    PRIMARY KEY ( `ID` )
    )type=InnoDB row_format=dynamic;

    alter table `test`.`Owners` add index `indexIDcar` ( IDcar );
    alter table `test`.`Owners` add foreign key (IDcar) references `Cars` (ID) on delete restrict;
     

    as the output of double clicking on my new tables in test. As you can see, the FK relationship exists in owners.

    The only 2 things I had to do were

    1: Change the last alter table to:

    Code:
    alter table `test`.`Owners` add foreign key (IDcar) references `Cars` (ID) on delete restrict;

    As I pointed out before, you were trying to reference cars.IDCar and that field does not exist. I changed it to Cars.ID and it works fine.

    2: Table names in MySQL are case sensitive. Since you created them with proper capitalization you HAVE to use that everywhere.

    HOWEVER I used the Manage Relations tool to delete the relationship and try and re-create it and it does not work. (Ritesh, we do have a problem here). I've submitted thisas a bug.

    in reply to: GENESIS – A MySql virgin #13630
    CalEvans
    Member

    QUOTE (himagain @ Feb 4 2003, 12:30 PM)
    Hello cal,

    Thanks for the sympathy and help! 🙂

    I will try it out.

    As a tyro I was/am looking for perhaps a *real* entry level tutorial on MySql.

    For example I couldn't even follow the “simple” instructions for SQLyog – the terms meant nothing! 🙁

    Grab yourself a copy of SQL for Dummies. It's the best reference I've found. Once you make it through that, Paul Dubois book on MySQL is good and of course, my favorite, Joe Celko's SQL for Smarties. It's more of a cookbook but it paid for itself the day I bought it.

    I don't know of many good tutorials on-line except for (as mentioned) MySql Dot Com I know of several good 'Using PHP with MySQL pages but that's doesn't sound like where you want to go.

    HTH,

    =C=

    in reply to: GENESIS – A MySql virgin #13629
    CalEvans
    Member

    QUOTE (himagain @ Feb 4 2003, 12:30 PM)
    Hello cal,

    Thanks for the sympathy and help! 🙂

    I will try it out.

    As a tyro I was/am looking for perhaps a *real* entry level tutorial on MySql.

    For example I couldn't even follow the “simple” instructions for SQLyog – the terms meant nothing! 🙁

    Grab yourself a copy of SQL for Dummies. It's the best reference I've found. Once you make it through that, Paul Dubois book on MySQL is good and of course, my favorite, Joe Celko's SQL for Smarties. It's more of a cookbook but it paid for itself the day I bought it.

    I don't know of many good tutorials on-line except for (as mentioned) MySql Dot Com I know of several good 'Using PHP with MySQL pages but that's doesn't sound like where you want to go.

    HTH,

    =C=

    in reply to: Foreign keys #13647
    CalEvans
    Member
    Quote:
    i think that Webyog 3.01 understands that I'm trying to do something different (in the SQL statement it writes IDcar two times).

    Danny,

    Can you be more specific?

    1: Are you trying to use the 'Manage Relationships' feature or are you writing the sql yourself and executing it in the command window?

    2: If you are using 'Manage Relationships' which table did you select before pressing the button? (Cars or Owners?)

    3: What relevant output are you getting? (check your mysql.err file, check you mysql.log file, check the Messages window of SQLyog)

    4: Can you post the output you described above where you get IDCar twice?

    Your code looks solid (without having actually executed it myself) Other than:

    Quote:
    alter table `test`.`owners` add foreign key (IDcar) references `cars` (IDcar) on delete restrict

    looks like it should be

    Quote:
    alter table `test`.`owners` add foreign key (IDcar) references `cars` (ID) on delete restrict

    I've used the Manage Relationships once and while it took a couple of tries to get it right (mainly my misunderstandings of how InnoDB worked) I was able to create the relationship I needed.

    HTH,

    =C=

    in reply to: InnoDB Table Type?!! #13625
    CalEvans
    Member

    What does the output of

    mysqladmin variables

    say? (Only the InnoDB stuff?)

    Also, immediately after trying it, check you error log for messages.

    If none there, check the regular log if you have logging turned on.

    =C=

    in reply to: Insert/Update data dialog #13641
    CalEvans
    Member
    Quote:
    I have been trying to find any mention of the check boxes on the left-hand side of the Insert/Update data dialog. What are they for please

    They are to mark records for deletion. Check the boxes next to the records you want to delete and then click on the Delete Records button. POOF! they are gone.

    They are nicely documented in the 'Virtual Docs' (Chapters 4-8 cover their use!) 😀

    HTH,

    =C=

    in reply to: Error 2003 #13643
    CalEvans
    Member
    Quote:
    Error 2003

    Can't connect to MySQL server on '207.44.212.27' (10060)

    The section of the docs covering this problem

    Gives you a couple things to check. Looks to me like you are trying to connect to MySQL on a port it's not running on.

    =C=

Viewing 15 posts - 241 through 255 (of 258 total)