liveBook · Manning

Deletion

Deletion is an operation that removes an item, association, or resource from a collection or system, or requests or marks it for removal.

How 8 Manning books explain it

Advanced Algorithms and Data Structures

Delete is an operation that removes a node or element from a data structure while preserving its structural invariants.

How it is used
Removes stored keys, points, or elements while keeping subsequent data-structure operations valid.
How deep it goes
Develops recursive pruning and replacement procedures, then addresses SS-tree occupancy repair rather than treating removal as a single update.
Examples
Uses an “anti” trie path, k-d tree node-replacement diagrams, and SS-tree point-deletion procedures.
What you can do after
Build it from scratch by implementing trie pruning or k-d tree replacement while checking each structure’s invariants.

Read how Advanced Algorithms and Data Structures explains deletion →

Django in Action

DELETE is an HTTP method that requests removal of a resource identified by a URL.

How it is used
Maps the delete part of CRUD onto an HTTP request that removes an API resource.
How deep it goes
Works through a Django Ninja endpoint from URL ID lookup to model deletion and 404 behavior.
Examples
Demonstrates deleting a Venue through /venue/{venue_id}/ and deleting a Musician model instance.
What you can do after
Build it from scratch as a Django Ninja route that locates, deletes, and reports on a resource.

Read how Django in Action explains deletion →

API Design Patterns

A delete method is an API operation that removes an existing resource.

How it is used
Removes resources while forcing explicit decisions about absence, authorization, repetition, and resource-specific support.
How deep it goes
Defines request shape and return behavior, then works through idempotence, status ambiguity, permissions, and soft-deletion changes.
Examples
Uses DeleteChatRoom, chatRooms/{id}, repeated deletion, immutable resources, and soft-deleted ChatRoom listing scenarios.
What you can do after
Operate/configure a delete endpoint with explicit absence, authorization, repetition, and soft-deletion policies.

Read how API Design Patterns explains deletion →

Pro ASP.NET Core 7, Tenth Edition

Delete is a response-cookie operation that instructs the client to remove a cookie.

How it is used
Uses response-cookie deletion to clear browser-held counters through a `/clear` endpoint.
How deep it goes
Shows the `Delete` calls, redirect, and response-header timing; does not detail browser cookie-removal mechanics.
Examples
Tests `/cookie` and `/clear` to observe incrementing counters reset after both cookies are deleted.
What you can do after
Apply it via `Response.Cookies.Delete` to clear named cookies before writing the response body.

Read how Pro ASP.NET Core 7, Tenth Edition explains deletion →

Building Web APIs with ASP.NET Core

DELETE is an HTTP request method for removing a resource.

How it is used
Implements resource removal as the delete operation in a board-game API’s CRUD workflow.
How deep it goes
Implements lookup, removal, persistence, and response construction while deferring authentication and authorization.
Examples
Tests deleting the Risk board game with ID 181 through Swagger UI.
What you can do after
Apply EF Core and HttpDelete to implement and test a resource-deletion endpoint.

Read how Building Web APIs with ASP.NET Core explains deletion →

ASP.NET Core in Action, 3e

Remove is an Entity Framework Core method that marks an entity for deletion when changes are saved.

How it is used
Uses Remove to delete entities with Entity Framework Core.
How deep it goes
Names Remove and cautions about deletion, without detailing its implementation.
Examples
Uses an IsDeleted flag as an example of a soft-delete alternative.
What you can do after
Evaluate whether entity deletion should be permanent or use a soft-delete flag.

Read how ASP.NET Core in Action, 3e explains deletion →

Build Python Web Apps with Streamlit

DELETE FROM is a SQL statement that removes rows from a table, optionally restricted by a condition.

How it is used
Removes selected rows from a table in a SQL CRUD workflow.
How deep it goes
Explains WHERE targeting, warns that omitting it deletes every row, and distinguishes deleting rows from dropping a table.
Examples
Uses a DELETE FROM statement to remove the haiku with ID 2.
What you can do after
Apply SQL DELETE FROM with a WHERE condition to remove a chosen row.

Read how Build Python Web Apps with Streamlit explains deletion →

100 Java Mistakes and How to Avoid Them

A collection removal method is an operation that removes matching elements or mappings from a collection or map.

How it is used
Prevents silent failures when removing collection elements or mappings with mismatched types or ambiguous overloads.
How deep it goes
Explains argument typing, overload binding, consequences, assertions, IDE hints, and library alternatives, but not collection implementation internals.
Examples
Uses List<Integer> removal, File-versus-Path containment, IDE parameter hints, and assertions that verify value removal.
What you can do after
Diagnose removal bugs by checking argument types, overload selection, boolean results, assertions, and IDE parameter hints.

Read how 100 Java Mistakes and How to Avoid Them explains deletion →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.