Views, Triggers & Procedures
What the database can do for you before your application sees the data.
0 of 17 answered
Start here
A view as a permission boundary
Foundation
- Not triedA view as a permission boundaryFoundation
- Not triedBEFORE or AFTERFoundation
- Not triedProcedure or functionFoundation
- Not triedTrigger or constraintFoundation
- Not triedWhat a materialised view trades awayFoundation
- Not triedWhat a view actually storesFoundation
- Not triedA bulk load that got slowCore
- Not triedAn audit row that should not existCore
- Not triedCounting round tripsCore
- Not triedViews built on viewsCore
- Not triedWhy this view refuses an UPDATECore
- Not triedA trigger that fires itselfChallenge
- Not triedMaking an unupdatable view writableChallenge
- Not triedThe insert that did four thingsChallenge
- Not triedThe loop inside the databaseChallenge
- Not triedThe row that vanishes after you insert itChallenge
- Not triedTwo triggers, one eventChallenge