To add a foreign key in SQLite, you need to follow these steps:
- Ensure you are using SQLite version 3.6.19 or higher, as foreign key support was added in this version.
- Create the main table (referred to as the parent table) using the CREATE TABLE statement. Define the primary key for this table using the PRIMARY KEY constraint.
- Create the child table that will have the foreign key reference (referred to as the child table) using the CREATE TABLE statement. Define the foreign key column using the FOREIGN KEY constraint.
- Specify the relationship between the parent and child table by setting the foreign key constraint. To do this, use the ALTER TABLE statement with the ADD CONSTRAINT keyword. Specify the foreign key column and the REFERENCES clause to indicate the parent table and the primary key column it references. Example: ALTER TABLE child_table ADD CONSTRAINT fk_name FOREIGN KEY (foreign_key_column) REFERENCES parent_table (primary_key_column); Note that the column names used in the foreign key constraint should match the respective column names in the tables.
- Enable foreign key constraints for your database connection by executing the PRAGMA foreign_keys = ON; command. This ensures that the foreign key constraints are enforced.
Once you have followed these steps, the foreign key relationship will be established between the two tables, and SQLite will enforce referential integrity by automatically checking and enforcing the constraints.
Best SQLite Books to Read in 2025
What is the significance of the ON DELETE CASCADE clause in a foreign key constraint in SQLite?
The ON DELETE CASCADE clause in a foreign key constraint in SQLite is used to specify the action that should be taken when a referenced row in the parent table is deleted.
When the ON DELETE CASCADE clause is included in a foreign key constraint, it means that if a row in the parent table is deleted, then all the rows in the child table that are referencing it will also be deleted automatically. This cascading effect ensures data integrity and consistency between the two tables.
The significance of the ON DELETE CASCADE clause is that it simplifies the process of deleting related rows in the child table when a referenced row in the parent table is removed. It saves developers from manually deleting each dependent row in the child table, reducing complexity and potential errors in managing data relationships.
However, it is important to use the ON DELETE CASCADE clause with caution as it can lead to unintended data loss if not implemented properly.
Are foreign keys supported in all versions of SQLite?
Yes, foreign keys are supported in all modern versions of SQLite, starting from version 3.6.19. However, it is important to note that foreign key support is not enabled by default. It needs to be specifically enabled for each database connection by executing the "PRAGMA foreign_keys = ON" command, or by configuring the database to enable foreign key support at compile time.
How can you check if a foreign key constraint exists in SQLite?
To check if a foreign key constraint exists in SQLite, you can use the following query:
1
|
PRAGMA foreign_key_list(table_name);
|
Replace table_name with the actual name of the table you want to check. This query will return a list of foreign key constraints for the specified table. If there are no foreign key constraints, an empty result will be returned.
Alternatively, you can use the sqlite_master table to check for the existence of foreign key constraints. Here's an example query:
1
|
SELECT name FROM sqlite_master WHERE type = 'table' AND sql LIKE '%FOREIGN KEY%';
|
This query will return the names of the tables that have foreign key constraints defined. If there are no foreign key constraints, an empty result will be returned.
