Re: Trigger Problem

Well, my job security notwithstanding, we have very little control over the database, triggers are one of the few things we can do to the db. This is also the only way that I could see to solve the problem - in a quick and dirty way.

"Pl/sql doesn't allow DDL" - even if I am intentionally trying to stay
away from that? Or does the fact the I let TOAD create outer shell of the trigger limit what I am trying to do? I tried to keep all commands to TRANSACT-SQL so that the PL part wouldn't come into play.

"You would need to use EXECUTE IMMEDIATE " - again - coming from a MS
SQL Server house, this is unfamiliar to me - as in 2 years of SQL programming against SQL Server 2000 I never once had to use it, or even be aware that it existed. Could you possibly provide some sort of example ( quick and dirty is fine )?

On a separate note ... why is the view inside the trigger, when you are only pulling 2 or 3 rows of data, a bad idea? It simplified the query (and lines of code)required to get the job done immensely, and has almost no effect on the database. And the view will NEVER be very big, as it gets replaced every fire - and will always be small. Received on Thu Oct 07 2004 - 13:20:43 CDT