Understanding the table generated by Django

The toys_toy table persists in the database the Toy class we recently created, specifically, the Toy model. Django's integrated ORM generated the toys_toy table based on our Toy model.

Run the following command to retrieve the SQL used to create the toys_toy table:

    sqlite3 db.sqlite3 ".schema toys_toy"

The following lines show the output for the previous command together with the SQL that the migrations process executed, to create the toys_toy table that persists the Toy model. The next lines are formatted to make it easier to understand the SQL code. Notice that the output from the command is formatted in a different way:

    CREATE TABLE IF NOT EXISTS "toys_toy" 
    (
        "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT,
        "created" datetime NOT NULL, 
        "name" varchar(150) NOT NULL, 
        "description" varchar(250) NOT NULL, 
        "toy_category" varchar(200) NOT NULL, 
        "release_date" datetime NOT NULL, 
        "was_included_in_home" bool NOT NULL
    );
  

The toys_toy table has the following columns (also known as fields) with their SQLite types, all of them not nullable:

• id: The integer primary key, an autoincrement row
• created: DateTime
• name: varchar(150)
• description: varchar(250)
• toy_category: varchar(200)
• release_date: DateTime
• was_included_in_home: bool