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

Error 1005

forums forums SQLyog Using SQLyog Error 1005

  • This topic is empty.
Viewing 6 reply threads
  • Author
    Posts
    • #9354
      gregharper
      Member

      I'm trying to create foeign keys. I keep getting an error Error 1005 Can't create table bookorama '.#sql-830_3d5.frm' (errno 139)

      I have been looking around everywhere for somting else to try…

      Windows XP Pro Service Pack2

      I'm running PHP 5.05

      MySQL 5.015

      SQLyog 4.07

      Thank You

    • #19743
      Ritesh
      Member

      Are you sure that the correct index is created on involved columns?

      More info at: http://dev.mysql.com/doc/refman/5.0/en/inn…onstraints.html

    • #19744
      peterlaursen
      Participant

      Is that the ONLY thing that you cannot ?

      Can you simply create ANY table using INNODB (without FK's)?

      I ask this because some ISP (silently) disable InnoDB.

      But the MySQL and PHP version tells me that it is probably is your own server. Right ? Is the server running on your local WinXP?

      And it is SQLyog that you are using? What do you use PHP for then?

      But if you use PHP you must use a webserver then too. Which one?

      And also please explain (screenshots are good!) EXACTLY where you are when you get this error message?

      We can't guess all those things. You must PIN IT OUT! 🙂

    • #19745
      gregharper
      Member
      peterlaursen wrote on Nov 14 2005, 02:24 AM:
      Is that the ONLY thing that you cannot ?

      Can you simply create ANY table using INNODB (without FK's)?

      I ask this because some ISP (silently) disable InnoDB.

      But the MySQL and PHP version tells me that it is probably is your own server.  Right ? Is the server running on your local WinXP?

      And it is SQLyog that you are using? What do you use PHP for then?

      But if you use PHP you must use a webserver then too.  Which one?

      And also please explain (screenshots are good!) EXACTLY where you are when you get this error message? 

      We can't guess all those things.  You must PIN IT OUT!  🙂

      [post=”7886″]<{POST_SNAPBACK}>[/post]

      I have no problem creating tables, This on my server at home. I do testing at home then bring it to work and see if i can run the apps. on CSC's setup.

      I did notice that phpmyadmin 2.70 beta1 which i just installed on thrusday night might have some issue's. When i was building the tables (I was just use to phpmyadmin) This release sets the UTF8 to some strange setting i have not seen before. I use PHP for webdevelopment at work. I create webforms to collect data form customers and our Employees. But within a few weeks they want to be able to query on stats for a four month period. and display gantt charts. So i thought if i could link the tables together they would be able to to perform the Query. I was using the examples from PH and MySQL WebDevelopment (third edition) ISBN 0-672-32672-8. I'm writing at work but when i get home i'll attach some screen shots…… I did get to create a a couple of links between tables. But then i just started getting the Error Message… And i have no problem creating Databases and Tables…

      Thank You

    • #19746
      peterlaursen
      Participant

      Well …

      I don't think phpMyAdmin works with php5 at all ?

      Correct me if I am wrong! But I have a Windows XP as well as a SUSE 10 Linux machine. The Yast installer on SUSE insists to uninstall myphpadmin if I upgrade from php4 to php5.

      It is noteworthy that practically ALL ISPs stay at php4 (not php5) php_mysql extension (not php_mysqli) and MySQL 4.0 or earlier. The main reason is I believe that they depend on phpmyadmin and thats why they don't upgrade the server and preprocessor software.

      I am not quite sure that I understand you completely, but if you did not allrady, then start from scratch and do EVERYTHING with SQLyog. If phpmyadmin has destroyed the table metadata everything could happen.

      Didn't you consider using SQLyog at work too?

    • #19747
      gregharper
      Member
      peterlaursen wrote on Nov 14 2005, 04:11 PM:
      Well …

      I don't think phpMyAdmin works with php5 at all ?

      Correct me if I am wrong!  But I have a Windows XP as well as a SUSE 10 Linux machine.  The Yast installer on SUSE insists to uninstall myphpadmin if I upgrade from php4 to php5.

      It is noteworthy that practically ALL ISPs stay at php4 (not php5) php_mysql extension (not php_mysqli) and MySQL 4.0 or earlier.  The main reason is I believe that they depend on phpmyadmin and thats why they don't upgrade the server and preprocessor software.

      I am not quite sure that I understand you completely, but if you did not allrady, then start from scratch and do EVERYTHING with SQLyog.  If phpmyadmin has destroyed the table metadata everything could happen.

      Didn't you consider using SQLyog at work too?

      [post=”7891″]<{POST_SNAPBACK}>[/post]

      I'm not dealing with ISP's, This running out of house. I just like to try different things out just to see if they work. I'll set things up at home then go into work and log on and see they everything runs OK.

      I was thinking the same thing. I'll redo the tables with SQLyog and yes i was thinking of using it work. You'll see some of the forms i'm working on for school. This is when i knew i going to have to deal with databases in another way to get some good results. Here is a link to my site at home, You'll see a link to screenshots. I'm not sure what you view .jpg with but i had to launch in Image Ready then viewed it in IE from the menu on the left hand side to see it in full screen…

      gregharper.com

      Thank you all so much for the help…

    • #19748
      peterlaursen
      Participant

      I saw your screenshots, but I am in doubt how I should understand all this!

      What is the situation like now?

      Do you still have questions/problems ?

Viewing 6 reply threads
  • You must be logged in to reply to this topic.