Foreign Keys
Go Up to Supported Objects
Foreign keys enforce referential integrity between tables by verifying the existence of foreign key values in the parent table before letting you insert or update foreign key values in the child table.
Creating and editing
- Foreign Keys Wizard (DB2 LUW) and Foreign Keys Editor (IBM DB2 LUW)
- Foreign Keys Wizard (DB2 Z/OS)) and Foreign Keys Editor (IBM DB2 Z/OS)
- Foreign Keys wizard (MySQL) and Foreign Keys editor (MySQL)
- Foreign Keys Wizard (Oracle) and Foreign Keys Editor (Oracle)
- Foreign Keys Wizard (PostgreSQL) and Foreign Keys Editor (PostgreSQL)
- Foreign Keys Wizard (SQL Server) and Foreign Keys Editor (SQL Server)
- Foreign Keys Wizard (Sybase ASE) and Foreign Keys Editor (Sybase ASE)
- Note: Creation and editing of objects of this type is not supported against Sybase IQ datasources.
DBMS platform availability and object actions/operations supported
The following table lists object actions available for this object type. For an introduction to object actions and details on usage of specific actions, see Object actions.
| DB2 LUW | DB2 z/OS | MySQL | ORCL | PSTGRS * | SQL SVR | SYB ASE | SYB IQ | |
|---|---|---|---|---|---|---|---|---|
|
✓ |
✓ |
|||||||
|
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ | ||
|
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ | ||
|
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
|||
|
✓ |
✓ |
✓ |
✓ |
✓ |
||||
|
✓ |
DBMS platform-specific notes
|
MySQL |
MySQL recognizes two types of tables, MyISAM and InnoDB. MyISAM tables access data records using an index, where InnoDB tables allow transactions and foreign keys. Therefore, the discussion of foreign keys is limited to your InnoDB tables. |