DROP_VIEW(7pg13)

💅 DROP VIEW (7pg13) 💅

okay so bestie, welcome to the PostgreSQL 13.23 Documentation page for DROP VIEW — yes, the manual name is folded right in near the top like a lil name tag 🎀. This is the whole glow-up of DROP_VIEW, and it's giving “remove a view” energy. ✨

---

🌸 NAME 🌸

DROP_VIEW — remove a view 💖

✨ SYNOPSIS ✨

DROP VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]

🦋 DESCRIPTION 🦋

DROP VIEW drops an existing view. Simple as that. No cap. To execute this command, you must be the owner of the view — like, it's their view, their rules, periodt. 💅

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the view does not exist. A notice is issued in this case. So if it's already gone, you get a lil notice instead of a whole error moment. 🙈
• name — the name (optionally schema-qualified) of the view to remove. That's the target, bestie. 🎯
• CASCADE — automatically drop objects that depend on the view (such as other views), and in turn all objects that depend on those objects (see Section 5.14). It's giving domino effect, lowkey. 🔥
• RESTRICT — refuse to drop the view if any objects depend on it. This is the default. Safe and sound, no cap. 🛡️

🌈 EXAMPLES 🌈

This command will remove the view called kinds:

DROP VIEW kinds;

Iconic. Simple. Slay. 💖

⭐ COMPATIBILITY ⭐

This command conforms to the SQL standard, except that the standard only allows one view to be dropped per command — and apart from the IF EXISTS option, which is a PostgreSQL extension. So yeah, standard-ish, but with a PostgreSQL twist. 💫

👑 SEE ALSO 👑

• ALTER VIEW (ALTER_VIEW(7))
• CREATE VIEW (CREATE_VIEW(7))

These are your besties for view-related lore. iykyk. 🫶

---

That's the whole vibe. This page is brought to you by PostgreSQL 13.23, dated 2025 — mwah, bye bestie! 💋✨