A few weeks ago, there was a question about disabling TRUNCATEs. That can be easily done via a Trigger.
SQL> -- create a trigger that raises an error on truncates
SQL> create or replace trigger prevent_truncates
2 before truncate on schema
4 raise_application_error(-20001,'TRUNCATE not permitted');
Here's a video by Stephane Faroult (RoughSea) : "Are you ready 2.0 ?"
A recent ComputerWorld article "How are students learning programming in a post-Basic world ?" (It should be BASIC, not Basic) reminds me of the time I first learnt programming.
Oracle ACEs in this part of the world had a conference call with Oracle's Program Executive for the APAC Developer Program.
A response recent forums question about handling an inequality condition also reminded me, once again, about NULL handling in Oracle.
You can have :
WHERE column = 100
in a query.
In another query, you could have
WHERE column != 100
However, if the column does contain a NULL in any one (or more rows), the union of the two queries is not the entire table. That is, rows with NULLs are excluded.
You have to specifically handle NULLs with either