Nesneleri Etkileşimli Olarak Oluşturma ve Kaydetme

The shell lets you create database rows by hand. Start by building an instance with the values you want.

That instance lives only in memory so far. The database knows nothing about it until you explicitly write it.

Call save() to insert the row. Django runs the SQL and your object now lives in the database for real.

After saving, your object gets a primary key in p.pk. A value means the insert succeeded and the row exists.

Prefer fewer steps? create() builds and saves in a single call, returning the finished object right away.

To update, change an attribute and call save() once more. Django writes only the new values to that row.

Confirm the write by fetching the row with get(). Seeing it returned proves your data really landed.

A fast sanity check is count(). It tells you how many rows the table holds after your inserts.

Clean up test data with delete() on an instance. The row is removed from the database immediately.

Remember these changes are permanent. The shell talks to your actual database, so avoid experimenting on production data.

This live flow is perfect for seeding a few rows while you build features, so pages have something to display.

Which call builds and saves a row in one step?

You created objects, used save() and create() to persist them, then read, counted, and deleted rows live in the shell. 💾