Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's a <a href="http://verysimple.com/2006/10/22/mysql-error-number-1005-cant-create-table-mydbsql-328_45frm-errno-150/" rel="noreferrer">nice checklist here</a>.</p> <blockquote> <p>Below is a running list of known causes that people have reported for the dreaded errno 150:</p> <ol> <li>The two key fields type and/or size is not an exact match. For example, if one is INT(10) the key field needs to be INT(10) as well and not INT(11) or TINYINT. You may want to confirm the field size using SHOW CREATE TABLE because Query Browser will sometimes visually show just INTEGER for both INT(10) and INT(11). You should also check that one is not SIGNED and the other is UNSIGNED. They both need to be exactly the same. (More about signed vs unsigned here).</li> <li>One of the key field that you are trying to reference does not have an index and/or is not a primary key. If one of the fields in the relationship is not a primary key, you must create an index for that field. (thanks to Venkatesh and Erichero and Terminally Incoherent for this tip)</li> <li>The foreign key name is a duplicate of an already existing key. Check that the name of your foreign key is unique within your database. Just add a few random characters to the end of your key name to test for this. (Thanks to Niels for this tip)</li> <li>One or both of your tables is a MyISAM table. In order to use foreign keys, the tables must both be InnoDB. (Actually, if both tables are MyISAM then you won’t get an error message – it just won’t create the key.) In Query Browser, you can specify the table type.</li> <li>You have specified a cascade ON DELETE SET NULL, but the relevant key field is set to NOT NULL. You can fix this by either changing your cascade or setting the field to allow NULL values. (Thanks to Sammy and J Jammin)</li> <li>Make sure that the Charset and Collate options are the same both at the table level as well as individual field level for the key columns. (Thanks to FRR for this tip)</li> <li>You have a default value (ie default=0) on your foreign key column (Thanks to Omar for the tip)</li> <li>One of the fields in the relationship is part of a combination (composite) key and does not have it’s own individual index. Even though the field has an index as part of the composite key, you must create a separate index for only that key field in order to use it in a constraint. (Thanks to Alex for this tip)</li> <li>You have a syntax error in your ALTER statement or you have mistyped one of the field names in the relationship (Thanks to Christian &amp; Mateo for the tip)</li> <li>The name of your foreign key exceeds the max length of 64 chars. (Thanks to Nyleta for the tip)</li> </ol> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POForeign Key add fails in MySQL with Error Code 1005, number 150
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdjechlin
    1. USKonerak
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POForeign Key add fails in MySQL with Error Code 1005, number 150
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO+1 Great link, Konerak
      singulars
      1. PO
      1. USJohan
    2. COTurns out that it was a table that got accidentally created as a MyISAM instead of a InnoDB. A very interesting way of ID-10-T error exposing itself.
      singulars
      1. PO
      1. USthaBadDawg
    3. COThat is a very useful link.
      singulars
      1. PO
      1. USMr Mikkél
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload